From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Salyzyn <salyzyn@android.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: linux-next: Tree for Oct 23
Date: Thu, 24 Oct 2019 07:45:59 +1100 [thread overview]
Message-ID: <20191024074559.4d815e3a@canb.auug.org.au> (raw)
In-Reply-To: <d1a0c336-1973-5c6d-90c0-9bb64e5a922c@android.com>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hi all,
On Wed, 23 Oct 2019 08:46:09 -0700 Mark Salyzyn <salyzyn@android.com> wrote:
>
> On 10/22/19 11:05 PM, Shaokun Zhang wrote:
> >
> > It's the commit <79f0cf35dccb> ("treewide: cleanup: replace prefered with preferred").
> Ack, will split up patch and resubmit, compiler differences make that
> part of the cleanup unworkable.
I have removed that patch from the akpm tree for now.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-23 20:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 4:55 linux-next: Tree for Oct 23 Stephen Rothwell
2019-10-23 6:05 ` Shaokun Zhang
2019-10-23 6:44 ` Geert Uytterhoeven
2019-10-23 6:56 ` Randy Dunlap
2019-10-23 6:57 ` Shaokun Zhang
2019-10-23 15:46 ` Mark Salyzyn
2019-10-23 20:45 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 5:58 Stephen Rothwell
2020-10-23 2:34 Stephen Rothwell
2014-10-23 4:21 Stephen Rothwell
2014-10-23 12:47 ` Stephen Rothwell
2013-10-23 15:13 Thierry Reding
2013-10-23 20:01 ` Guenter Roeck
2013-10-24 7:20 ` Sedat Dilek
2013-10-24 7:41 ` Thierry Reding
2012-10-23 4:19 Stephen Rothwell
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=20191024074559.4d815e3a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=salyzyn@android.com \
--cc=zhangshaokun@hisilicon.com \
/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).