From: Alex Elder <alex.elder@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>, Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dianders@chromium.org,
caleb.connolly@linaro.org, mka@chromium.org,
evgreen@chromium.org, andersson@kernel.org,
quic_cpratapa@quicinc.com, quic_avuyyuru@quicinc.com,
quic_jponduru@quicinc.com, quic_subashab@quicinc.com,
elder@kernel.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] net: ipa: only reset hashed tables when supported
Date: Tue, 25 Jul 2023 07:31:13 -0500 [thread overview]
Message-ID: <f0fb38cb-ed2f-d09d-7675-97291d1bc2cc@linaro.org> (raw)
In-Reply-To: <2023072538-corned-falsify-d054@gregkh>
On 7/25/23 2:08 AM, Greg KH wrote:
> You sent 2 different versions of this patch? Which one is for what
> tree? Is this in Linus's tree already? If so, what's the git id?
It was a mistake. I reached out to the netdev maintainers
yesterday to explain and I'm sorry I didn't do the same for
you/stable.
One of those patches will be brought upstream the normal
netdev way. Back-porting to 6.1 won't work cleanly--and
once it's upstream I'll provide the other one if required.
I'm really sorry to have caused the confusion.
-Alex
next prev parent reply other threads:[~2023-07-25 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 22:41 [PATCH net] net: ipa: only reset hashed tables when supported Alex Elder
2023-07-25 7:08 ` Greg KH
2023-07-25 12:31 ` Alex Elder [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 22:40 Alex Elder
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=f0fb38cb-ed2f-d09d-7675-97291d1bc2cc@linaro.org \
--to=alex.elder@linaro.org \
--cc=andersson@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_avuyyuru@quicinc.com \
--cc=quic_cpratapa@quicinc.com \
--cc=quic_jponduru@quicinc.com \
--cc=quic_subashab@quicinc.com \
--cc=stable@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 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.