From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.van@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wireless dependency
Date: Thu, 18 Feb 2016 15:22:22 +0200 [thread overview]
Message-ID: <87egcarw4x.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAF7Mx6rQrsxkm1g9O6-dkzQPLgV0X3yb5TakrOU316Xy-bU1pw@mail.gmail.com> (Arend Van Spriel's message of "Mon, 15 Feb 2016 11:16:49 +0100")
Arend Van Spriel <arend.van@broadcom.com> writes:
> I am preparing a patch series for wireless-drivers-next, but there is
> a dependency with patch that was submitted to wireless-drivers [1].
> How should I handle this. Can I submit it for wireless-drivers-next as
> well?
>
> [1] https://patchwork.kernel.org/patch/8061031/
Commiting the same patch twice is not acceptable. I think the easiest is
that you submit the dependency patches separately and document in patch
(after "---" line) or in the cover letter what commits you need from
wireless-drivers and why. I can then merge wireless-drivers to
wireless-drivers-next.
--
Kalle Valo
next prev parent reply other threads:[~2016-02-18 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 10:16 wireless dependency Arend Van Spriel
2016-02-18 13:22 ` Kalle Valo [this message]
2016-02-18 13:43 ` Kalle Valo
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=87egcarw4x.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend.van@broadcom.com \
--cc=linux-wireless@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