From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 59/73] drivers/gpio: delete non-required instances of include <linux/init.h>
Date: Wed, 5 Feb 2014 10:00:25 -0500 [thread overview]
Message-ID: <52F25209.2010506@windriver.com> (raw)
In-Reply-To: <CACRpkdYF2f1Ekp6JYwntj+UhbceWtMN==yKC7emsXHfktcZZsg@mail.gmail.com>
On 14-02-05 08:02 AM, Linus Walleij wrote:
> On Fri, Jan 24, 2014 at 3:21 AM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
>
>> For what it is worth, I'm not removing any patches from my series file
>> until they explicitly conflict and/or become redundant. If a maintainer
>> says they are adding the patch, I add a comment in the series file, but
>> I don't remove them until I see them come into next via another branch,
>> and/or sfr reports a conflict/redundancy.
>
> So I can add these patches to my devel branches now I think?
The patches that weren't taken by maintainers before 3.14-rc1 were
encompassed in the cleanup pull request to Linus sent yesterday.
http://www.spinics.net/lists/arm-kernel/msg304864.html
So, assuming he does pull it, you'll not have to do anything.
Thanks,
Paul.
--
>
> Yours,
> Linus Walleij
>
next prev parent reply other threads:[~2014-02-05 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1390339396-3479-1-git-send-email-paul.gortmaker@windriver.com>
2014-01-21 21:23 ` [PATCH 59/73] drivers/gpio: delete non-required instances of include <linux/init.h> Paul Gortmaker
2014-01-23 8:12 ` Linus Walleij
2014-01-23 22:58 ` Stephen Rothwell
2014-01-24 2:21 ` Paul Gortmaker
2014-02-05 13:02 ` Linus Walleij
2014-02-05 15:00 ` Paul Gortmaker [this message]
2014-02-06 9:33 ` Linus Walleij
2014-01-24 8:44 ` Linus Walleij
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=52F25209.2010506@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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).