linux-kernel - Re: staging tree closed for 3.7

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]

Message-ID: <20120927153515.GA1555@kroah.com>
Date:	Thu, 27 Sep 2012 08:35:15 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Ian Abbott <abbotti@....co.uk>
Cc:	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	H Hartley Sweeten <hartleys@...ionengravers.com>,
	Ian Abbott <ian.abbott@....co.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: staging tree closed for 3.7

On Thu, Sep 27, 2012 at 10:31:17AM +0100, Ian Abbott wrote:
> On 2012-09-26 18:56, Greg Kroah-Hartman wrote:
> >On Wed, Sep 26, 2012 at 10:56:06AM -0700, Greg Kroah-Hartman wrote:
> >>
> >>With 3.6 about to be released, I've now closed the 3.7 staging-next tree
> >>for new features / cleanups.  It's bug-fixes only now until 3.7-rc1 is
> >>out.
> >
> >Oh, and if I've missed any patches that people have sent me already,
> >please let me know, because I don't have them anymore.
> 
> I have an outstanding patch for the jr3_pci driver that was mostly
> __iomem tagging, but also included a one-line fix for an invalid
> iomem dereference.  Do you want me to resend the whole patch or just
> split out the one-line fix for 3.6?

The one line fix for now would be great, and then the __iomem one to
apply after that for 3.7 would be also ok.

Can you resend those?

thanks,

greg k-h
--
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/