From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>,
"abbotti@mev.co.uk" <abbotti@mev.co.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: comedi: adl_pci7296: factor out the PCI device code
Date: Wed, 23 May 2012 19:11:02 -0700 [thread overview]
Message-ID: <20120524021102.GA12335@kroah.com> (raw)
In-Reply-To: <20120523220702.GR4637@mwanda>
On Thu, May 24, 2012 at 01:07:02AM +0300, Dan Carpenter wrote:
> On Wed, May 23, 2012 at 04:52:47PM -0500, H Hartley Sweeten wrote:
> > On Wednesday, May 23, 2012 2:44 PM, Dan Carpenter wrote:
> > > Hartley, you're doing a great job with all these patches, but it's
> > > going to be weeks before the merge window closes. We're going to
> > > end up getting confused with all the patches floating around.
> >
> > I guess I should wait until the merge window closes and Greg starts
> > taking patches into the staging tree before continuing...
> >
>
> Wait! No no. The first answer was the right one, where you
> volunteered to do a bunch of work.
Yes, that's right, don't stop, I can queue these all up in my "to-apply"
mailbox just fine and will start applying them when 3.5-rc1 is out, to
my staging-next tree. No need for you to take a break at all :)
thanks,
greg k-h
prev parent reply other threads:[~2012-05-24 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 21:28 [PATCH] staging: comedi: adl_pci7296: factor out the PCI device code H Hartley Sweeten
2012-05-23 21:43 ` Dan Carpenter
2012-05-23 21:43 ` H Hartley Sweeten
2012-05-24 6:32 ` Dan Carpenter
2012-05-23 21:52 ` H Hartley Sweeten
2012-05-23 22:07 ` Dan Carpenter
2012-05-24 2:11 ` gregkh [this message]
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=20120524021102.GA12335@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=hartleys@visionengravers.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox