From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: linux-next@vger•kernel.org, Linus <torvalds@linux-foundation•org>,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: linux-next: please add queue for removal of __cpuinit and friends.
Date: Wed, 26 Jun 2013 11:22:02 +1000 [thread overview]
Message-ID: <20130626112202.0929939fdc416f23d4bc06fa@canb.auug.org.au> (raw)
In-Reply-To: <20130625152702.GA27288@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
Hi Paul,
On Tue, 25 Jun 2013 11:27:02 -0400 Paul Gortmaker <paul.gortmaker@windriver•com> wrote:
>
> 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?
Maybe. I will see how much pain it causes me.
> 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
Yeah, I should have responded to that. Given that the meat of this
series is the first 2 patches (the rest is merely cleaning up the uses of
the now mulled out macros, right) I think it would have been better (i.e.
easier for me :-)) if you had a git tree based on v3.10-rc<something> and
then did a sweep after v3.11-rc1 was out to clean up the rest.
> 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.
The problem is that it is based on shifting sands i.e. linux-next. This
means that I will have to rebase it each day onto the new linux-next just
before I release it. I already do this with Andrew's tree and that is a
bit of a pain already.
It also means (given that some linus-next included trees do not actually
get merged for -rc1), that some of these patches may never apply cleanly
to Linus' tree.
I will try it today and see how we go. I assume that the current set of
patches is based on next-20130625?
--
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-26 1:22 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 [this message]
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=20130626112202.0929939fdc416f23d4bc06fa@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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