From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 1 more question about sending patches with dependencies
Date: Fri, 26 Aug 2011 10:30:15 -0400 [thread overview]
Message-ID: <20110826143015.GG2579@tuxdriver.com> (raw)
In-Reply-To: <CACna6rwzzV=YSkATvLwKk4fcEgtiOjQ9+VihSet_og+y4KkqpA@mail.gmail.com>
On Fri, Aug 26, 2011 at 11:43:48AM +0200, Rafał Miłecki wrote:
> I want to send patch that depends on
> [RFC/RFT] b43: Relax requirement for descriptors to be in the DMA zone
>
> I guess this is already in the John's queue, as Michael asked to apply
> it even despite the fact it's RFC/RFT.
>
> Do I have to wait until pushing that patch into wireless-next /
> wireless-testing? Or can I just submit my patch? Or should I re-submit
> the mentioned patch as part of my patchset?
Yes, please repost it (with [PATCH] and Michael's S-o-b) as part of
your series.
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-08-26 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 9:43 1 more question about sending patches with dependencies Rafał Miłecki
2011-08-26 14:30 ` John W. Linville [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=20110826143015.GG2579@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).