From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
H Hartley Sweeten <hartleys@visionengravers.com>,
Ian Abbott <ian.abbott@mev.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: staging tree closed for 3.7
Date: Thu, 27 Sep 2012 08:35:15 -0700 [thread overview]
Message-ID: <20120927153515.GA1555@kroah.com> (raw)
In-Reply-To: <50641CE5.8070107@mev.co.uk>
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
next prev parent reply other threads:[~2012-09-27 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 17:56 staging tree closed for 3.7 Greg Kroah-Hartman
2012-09-26 17:56 ` Greg Kroah-Hartman
2012-09-26 18:47 ` H Hartley Sweeten
2012-09-26 20:05 ` Greg Kroah-Hartman
2012-09-26 21:13 ` H Hartley Sweeten
2012-09-27 9:31 ` Ian Abbott
2012-09-27 15:35 ` Greg Kroah-Hartman [this message]
2012-09-27 16:48 ` Ian Abbott
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=20120927153515.GA1555@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=devel@linuxdriverproject.org \
--cc=hartleys@visionengravers.com \
--cc=ian.abbott@mev.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.