From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
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: Fri, 28 Jun 2013 11:09:55 +1000 [thread overview]
Message-ID: <20130628110955.31ccbb49fa088c35449e7741@canb.auug.org.au> (raw)
In-Reply-To: <20130627173225.3915d976.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
Hi Andrew,
On Thu, 27 Jun 2013 17:32:25 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Fri, 28 Jun 2013 09:57:12 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > On Thu, 27 Jun 2013 16:37:33 -0700 akpm@linux-foundation.org wrote:
> > >
> > > 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.
OK, I shoved them back in (in akpm-current). One note:
$ git am ../../mmotm/text/broken-out/arch-c6x-mm-include-asm-uaccessh-to-pass-compiling.patch
Applying: arch: c6x: mm: include "asm/uaccess.h" to pass compiling
Warning: commit message did not conform to UTF-8.
You may want to amend it after fixing the message, or set the config
variable i18n.commitencoding to the encoding your project uses.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-28 1:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 23:37 akpm
2013-06-27 23:57 ` Stephen Rothwell
2013-06-28 0:32 ` Andrew Morton
2013-06-28 1:09 ` Stephen Rothwell [this message]
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=20130628110955.31ccbb49fa088c35449e7741@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=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 \
/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