* wireless dependency
@ 2016-02-15 10:16 Arend Van Spriel
2016-02-18 13:22 ` Kalle Valo
0 siblings, 1 reply; 3+ messages in thread
From: Arend Van Spriel @ 2016-02-15 10:16 UTC (permalink / raw)
To: Kalle Valo, linux-wireless
Hi Kalle,
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?
Regards,
Arend
[1] https://patchwork.kernel.org/patch/8061031/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: wireless dependency
2016-02-15 10:16 wireless dependency Arend Van Spriel
@ 2016-02-18 13:22 ` Kalle Valo
2016-02-18 13:43 ` Kalle Valo
0 siblings, 1 reply; 3+ messages in thread
From: Kalle Valo @ 2016-02-18 13:22 UTC (permalink / raw)
To: Arend Van Spriel; +Cc: linux-wireless
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: wireless dependency
2016-02-18 13:22 ` Kalle Valo
@ 2016-02-18 13:43 ` Kalle Valo
0 siblings, 0 replies; 3+ messages in thread
From: Kalle Valo @ 2016-02-18 13:43 UTC (permalink / raw)
To: Arend Van Spriel; +Cc: linux-wireless
Kalle Valo <kvalo@codeaurora.org> writes:
> 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.
I just checked and the commit is already in net-next (I guess via net
tree) so there's actually no problem. This commit should be in
wireless-drivers-next in next few minutes (as soon as the compilation
finishes).
I also saw that you already submitted the patches you were talking
about. I can just drop the duplicate patch, no need to resend anything
because of this.
commit e0045bf80f62779ba75ba04513020d60e59f5298
Author: Hante Meuleman <meuleman@broadcom.com>
Date: Tue Jan 19 12:39:24 2016 +0100
brcmfmac: fix sdio sg table alloc crash
--
Kalle Valo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-02-18 13:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-15 10:16 wireless dependency Arend Van Spriel
2016-02-18 13:22 ` Kalle Valo
2016-02-18 13:43 ` Kalle Valo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox