From: Dan Carpenter <dan.carpenter@oracle.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org, fmhess@users.sourceforge.net,
abbotti@mev.co.uk, gregkh@linuxfoundation.org
Subject: Re: [PATCH] staging: comedi: adl_pci7296: factor out the PCI device code
Date: Thu, 24 May 2012 00:43:54 +0300 [thread overview]
Message-ID: <20120523214354.GQ4637@mwanda> (raw)
In-Reply-To: <201205231428.48061.hartleys@visionengravers.com>
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.
Do you think you could maybe put up a git tree with the current
stuff so people know when they're stepping on each other's toes?
regards,
dan carpenter
next prev parent reply other threads:[~2012-05-23 21:40 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 [this message]
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
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=20120523214354.GQ4637@mwanda \
--to=dan.carpenter@oracle.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--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