From: Kalle Valo <kvalo@codeaurora.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Loic Poulain <loic.poulain@linaro.org>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, bbhatt@codeaurora.org,
willemdebruijn.kernel@gmail.com, jhugo@codeaurora.org,
hemantk@codeaurora.org, ath11k@lists.infradead.org
Subject: Re: [PATCH v10 1/2] bus: mhi: Add mhi_queue_is_full function
Date: Tue, 10 Nov 2020 20:44:06 +0200 [thread overview]
Message-ID: <87a6vp59xl.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <20201106083918.5ea0674b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (Jakub Kicinski's message of "Fri, 6 Nov 2020 08:39:18 -0800")
+ ath11k list
Jakub Kicinski <kuba@kernel.org> writes:
> On Fri, 06 Nov 2020 21:58:12 +0530 Manivannan Sadhasivam wrote:
>>>> Since you've applied now, what would you propose?
>>>
>>> Do you need mhi_queue_is_full() in other branches, or are you just
>>> concerned about the conflicts?
>>
>> Yes, I need this patch in mhi-next.
>>
>>> I'm assuming the concern is just about the mhi/core patch, or would
>>> you need to refactor something in the net driver as well?
>>
>> Just the mhi_queue_is_full() patch.
>
> Okay, I think you can just apply that patch to your tree again and git
> should figure out it's a duplicate. Not optimal, because the change will
> have two hashes, but the function is trivial, shouldn't be an issue
> even if conflict happens.
>
> Will you need it in wireless (ath11k), or only in other trees?
>
> If it ends up in the wireless tree Dave or I will do the resolution when
> we pull from Kalle so it won't even appear to Linus (but then it should
> go into wireless through an immutable branch).
I think in the next few releases we need close coordination between mhi
and ath11k, both are in active development and there can be changes
which break ath11k functionality. Let's see how this goes.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: willemdebruijn.kernel@gmail.com,
Loic Poulain <loic.poulain@linaro.org>,
jhugo@codeaurora.org, netdev@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
bbhatt@codeaurora.org, ath11k@lists.infradead.org,
linux-arm-msm@vger.kernel.org, hemantk@codeaurora.org,
davem@davemloft.net
Subject: Re: [PATCH v10 1/2] bus: mhi: Add mhi_queue_is_full function
Date: Tue, 10 Nov 2020 20:44:06 +0200 [thread overview]
Message-ID: <87a6vp59xl.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <20201106083918.5ea0674b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (Jakub Kicinski's message of "Fri, 6 Nov 2020 08:39:18 -0800")
+ ath11k list
Jakub Kicinski <kuba@kernel.org> writes:
> On Fri, 06 Nov 2020 21:58:12 +0530 Manivannan Sadhasivam wrote:
>>>> Since you've applied now, what would you propose?
>>>
>>> Do you need mhi_queue_is_full() in other branches, or are you just
>>> concerned about the conflicts?
>>
>> Yes, I need this patch in mhi-next.
>>
>>> I'm assuming the concern is just about the mhi/core patch, or would
>>> you need to refactor something in the net driver as well?
>>
>> Just the mhi_queue_is_full() patch.
>
> Okay, I think you can just apply that patch to your tree again and git
> should figure out it's a duplicate. Not optimal, because the change will
> have two hashes, but the function is trivial, shouldn't be an issue
> even if conflict happens.
>
> Will you need it in wireless (ath11k), or only in other trees?
>
> If it ends up in the wireless tree Dave or I will do the resolution when
> we pull from Kalle so it won't even appear to Linus (but then it should
> go into wireless through an immutable branch).
I think in the next few releases we need close coordination between mhi
and ath11k, both are in active development and there can be changes
which break ath11k functionality. Let's see how this goes.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-11-10 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 17:23 [PATCH v10 1/2] bus: mhi: Add mhi_queue_is_full function Loic Poulain
2020-11-03 17:23 ` [PATCH v10 2/2] net: Add mhi-net driver Loic Poulain
2020-11-06 0:57 ` Jakub Kicinski
2020-11-06 0:57 ` [PATCH v10 1/2] bus: mhi: Add mhi_queue_is_full function Jakub Kicinski
2020-11-06 5:13 ` Manivannan Sadhasivam
2020-11-06 16:04 ` Jakub Kicinski
2020-11-06 16:28 ` Manivannan Sadhasivam
2020-11-06 16:39 ` Jakub Kicinski
2020-11-10 18:44 ` Kalle Valo [this message]
2020-11-10 18:44 ` Kalle Valo
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm
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=87a6vp59xl.fsf@tynnyri.adurom.net \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=bbhatt@codeaurora.org \
--cc=davem@davemloft.net \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.