linux-kernel - Re: [PATCH 59/73] drivers/gpio: delete non-required instances of include <linux/init.h>

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Jan 2014 21:21:55 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Linus Walleij <linus.walleij@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	Alexandre Courbot <gnurou@...il.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 59/73] drivers/gpio: delete non-required instances of
 include <linux/init.h>

[Re: [PATCH 59/73] drivers/gpio: delete non-required instances of include <linux/init.h>] On 24/01/2014 (Fri 09:58) Stephen Rothwell wrote:

> Hi Linus,
> 
> On Thu, 23 Jan 2014 09:12:43 +0100 Linus Walleij <linus.walleij@...aro.org> wrote:
> >
> > On Tue, Jan 21, 2014 at 10:23 PM, Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
> > 
> > > None of these files are actually using any __init type directives
> > > and hence don't need to include <linux/init.h>.  Most are just a
> > > left over from __devinit and __cpuinit removal, or simply due to
> > > code getting copied from one driver to the next.
> > >
> > > Cc: Linus Walleij <linus.walleij@...aro.org>
> > > Cc: Alexandre Courbot <gnurou@...il.com>
> > > Cc: linux-gpio@...r.kernel.org
> > > Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
> > 
> > Patch applied for v3.15.
> 
> Yet that patch is in linux-next today.  And just 2 days ago I mailed out this request (as I do during each merge window):
> 
> "Please do not add any code intended for v3.15 to your linux-next included
> trees until after v3.14-rc1 has been released."
> 
> I have no problem with that particular patch being sent to Linus during
> this merge window (in fact Paul intends to send whatever is left of the
> series at the end of the merge window), but it makes me wonder about the
> other commits that you have added to the gpio tree (and the pinctrl tree)
> today.  Are they intended for this merge window or v3.15?

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.

Thanks,
Paul.
--

> -- 
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/