From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: linux-next: please add queue for removal of __cpuinit and friends.
Date: Wed, 26 Jun 2013 12:01:12 -0400 [thread overview]
Message-ID: <20130626160112.GB2172@windriver.com> (raw)
In-Reply-To: <20130626173822.957f35baad3637092bb61a7d@canb.auug.org.au>
[Re: linux-next: please add queue for removal of __cpuinit and friends.] On 26/06/2013 (Wed 17:38) Stephen Rothwell wrote:
> Hi Paul,
>
> On Wed, 26 Jun 2013 11:22:02 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > I will try it today and see how we go. I assume that the current set of
> > patches is based on next-20130625?
>
> OK, its in today. Just for info (at the end of today's linux-next):
>
> $ git grep -l __cpuinit
> arch/arm/mach-keystone/platsmp.c
> arch/arm/mach-sti/platsmp.c
> arch/mips/ath79/setup.c
> arch/mips/cavium-octeon/octeon-irq.c
> arch/mips/cavium-octeon/smp.c
[...]
> arch/mips/kernel/bmips_vec.S
> arch/mips/kernel/head.S
> arch/mips/mm/cex-sb1.S
> arch/mips/netlogic/common/smpboot.S
> include/linux/init.h
>
> So I guess the Ralf hasn't put the mips patch in his mips-for-linux-next
> branch yet. And a few more uses have crept in. :-(
Odd. It was in mips-for-linux-next on the 20th. Accidentally dropped?
I've re-inserted the mips patch into my patch queue, fixed up the new
uses that crept in, and refreshed the arm patch that gained a conflict.
Thanks,
Paul.
--
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
next prev parent reply other threads:[~2013-06-26 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 15:27 linux-next: please add queue for removal of __cpuinit and friends Paul Gortmaker
2013-06-26 1:22 ` Stephen Rothwell
2013-06-26 7:38 ` Stephen Rothwell
2013-06-26 16:01 ` Paul Gortmaker [this message]
2013-06-26 17:47 ` Paul Gortmaker
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=20130626160112.GB2172@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=linux-next@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).