From: Andrew Morton <akpm@linux-foundation•org>
To: Frederic Weisbecker <fweisbec@gmail•com>
Cc: linux-kernel@vger•kernel.org, linux-mm@kvack•org,
linux-fsdevel@vger•kernel.org, linux-next@vger•kernel.org
Subject: Re: mmotm 2013-05-09-15-57 uploaded
Date: Mon, 20 May 2013 15:31:35 -0700 [thread overview]
Message-ID: <20130520153135.a47e21227a4fc3a77996b482@linux-foundation.org> (raw)
In-Reply-To: <CAFTL4hwvP7GsrNTc4knQRMV1YHXnZRes=E_NpLAKSOgqTeou5g@mail.gmail.com>
On Mon, 20 May 2013 11:42:09 +0200 Frederic Weisbecker <fweisbec@gmail•com> wrote:
> Hi Andrew,
>
> 2013/5/10 <akpm@linux-foundation•org>:
> [...]
> > * posix_cpu_timer-consolidate-expiry-time-type.patch
> > * posix_cpu_timers-consolidate-timer-list-cleanups.patch
> > * posix_cpu_timers-consolidate-expired-timers-check.patch
> > * selftests-add-basic-posix-timers-selftests.patch
> > * posix-timers-correctly-get-dying-task-time-sample-in-posix_cpu_timer_schedule.patch
> > * posix_timers-fix-racy-timer-delta-caching-on-task-exit.patch
>
> Do you have any plans concerning these patches? These seem to have
> missed this merge window.
They're in my queue of "stuff to send to tglx" when I do my next
maintainer patchbombing.
I guess I should have done that significantly before the 3.10 release,
but it's rather discouraging how few of those patches get applied by
anyone. Maybe the solution to that is to send them more often, not
less.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack•org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack•org"> email@kvack•org </a>
prev parent reply other threads:[~2013-05-20 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 22:58 mmotm 2013-05-09-15-57 uploaded akpm
2013-05-20 9:42 ` Frederic Weisbecker
2013-05-20 22:31 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130520153135.a47e21227a4fc3a77996b482@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=fweisbec@gmail$(echo .)com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox