linux-kernel - Re: [git pull] gpio changes for $NEXT

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 27 May 2011 11:14:49 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-next <linux-next@...r.kernel.org>
Subject: Re: [git pull] gpio changes for $NEXT_KERNEL

Hi Grant,

On Thu, 26 May 2011 12:12:02 -0600 Grant Likely <grant.likely@...retlab.ca> wrote:
>
> Due to my own stupidity, this branch as /not/ been tested through
> linux-next.  I put it in a branch that I negelcted to ask Stephen to
> include.  :-(  I'm asking him to add it for tonight.  At the very
> least, it has been build tested on various x86, powerpc, mips, sparc
> and arm defconfigs.
> 
> You'll probably want to hold off on actually pulling this one, but I
> wanted to give you a heads up that I have it still pending.  If you've
> not picked it up, then I can resend the pull req tomorrow afternoon
> after confirming it hasn't messed up anything in linux-next.
> 
> There's nothing earth shattering here.  Just a bunch of driver updates
> and some faltering steps towards unifying a bunch of the mmio gpio
> logic.
> 
> g.
> 
> The following changes since commit 4db70f73e56961b9bcdfd0c36c62847a18b7dbb5:
> 
>   tmpfs: fix XATTR N overriding POSIX_ACL Y (2011-05-25 19:53:02 -0700)
> 
> are available in the git repository at:
>   git://git.secretlab.ca/git/linux-2.6 gpio/next

I have added this tree even though it looks like Linus took it - just in
case there is more stuff.

If you think it is unnecessary, let me know.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

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

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

Content of type "application/pgp-signature" skipped