From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: mmotm 2013-06-27-16-36 uploaded
Date: Thu, 27 Jun 2013 17:32:25 -0700 [thread overview]
Message-ID: <20130627173225.3915d976.akpm@linux-foundation.org> (raw)
In-Reply-To: <20130628095712.120bec7036284584fd467ee2@canb.auug.org.au>
On Fri, 28 Jun 2013 09:57:12 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Thu, 27 Jun 2013 16:37:33 -0700 akpm@linux-foundation.org wrote:
> >
> > The mm-of-the-moment snapshot 2013-06-27-16-36 has been uploaded to
> >
> > http://www.ozlabs.org/~akpm/mmotm/
> >
> > include-linux-smph-on_each_cpu-switch-back-to-a-macro.patch
> > arch-c6x-mm-include-asm-uaccessh-to-pass-compiling.patch
> > drivers-dma-pl330c-fix-locking-in-pl330_free_chan_resources.patch
>
> Did you mean to drop these three patches from linux-next?
Nope, they should be inside the NEXT_PATCHES_START/NEXT_PATCHES_END
section, thanks.
--
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>
next prev parent reply other threads:[~2013-06-28 0:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 23:37 mmotm 2013-06-27-16-36 uploaded akpm
2013-06-27 23:57 ` Stephen Rothwell
2013-06-28 0:32 ` Andrew Morton [this message]
2013-06-28 1:09 ` Stephen Rothwell
2013-06-28 5:30 ` mmotm 2013-06-27-16-36 uploaded (wait event common) Randy Dunlap
2013-06-28 5:51 ` Andrew Morton
2013-06-28 6:06 ` Randy Dunlap
2013-06-28 6:56 ` Stephen Rothwell
2013-06-28 15:38 ` Oleg Nesterov
2013-06-28 17:15 ` Oleg Nesterov
2013-06-29 14:00 ` Valdis.Kletnieks
2013-06-30 18:28 ` Oleg Nesterov
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=20130627173225.3915d976.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).