linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: linux-next: please add queue for removal of __cpuinit and friends.
Date: Tue, 25 Jun 2013 11:27:02 -0400	[thread overview]
Message-ID: <20130625152702.GA27288@windriver.com> (raw)

Hi Stephen,

Would you please add the patch queue below to linux-next for
the remainder of this week and the two weeks of the merge window?

It is the patch queue for removal of __cpuinit ; a git repository
of patches with a series file that can be browsed here:

  http://git.kernel.org/cgit/linux/kernel/git/paulg/cpuinit-delete.git

or cloned directly from here:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulg/cpuinit-delete.git

and the deletion and merge strategy was described here previously:

  https://lkml.org/lkml/2013/6/20/513

I have been tracking it manually myself by re-applying it locally
to the daily linux-next tree each day for a while now (you can see
patch refresh history in the repo for anyone wishing that level of
detail).

I do not expect any significant changes to the repository going forward.
Perhaps adding a couple more "Acked-by:" tags, and dropping a couple
patches for when maintainers request to carry them locally.  So I hope
it should not be a big burden.  And it is a one-shot tree as well.

Thanks,
Paul.
--

             reply	other threads:[~2013-06-25 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 15:27 Paul Gortmaker [this message]
2013-06-26  1:22 ` linux-next: please add queue for removal of __cpuinit and friends Stephen Rothwell
2013-06-26  7:38   ` Stephen Rothwell
2013-06-26 16:01     ` Paul Gortmaker
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=20130625152702.GA27288@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-next@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).