From: Jakub Kicinski <kuba@kernel.org>
To: patchwork-bot+netdevbpf@kernel.org
Cc: Alex Elder <elder@linaro.org>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
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
Subject: Re: [PATCH net-next v2 0/6] net: ipa: simplify IPA interrupt handling
Date: Thu, 5 Jan 2023 22:17:08 -0800 [thread overview]
Message-ID: <20230105221708.659069f1@kernel.org> (raw)
In-Reply-To: <167298541710.969.9209439108124310998.git-patchwork-notify@kernel.org>
On Fri, 06 Jan 2023 06:10:17 +0000 patchwork-bot+netdevbpf@kernel.org
wrote:
> - [net-next,v2,6/6] net: ipa: don't maintain IPA interrupt handler array
> (no matching commit)
Hm, no idea why it thinks this patch was not applied.
prev parent reply other threads:[~2023-01-06 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 17:52 [PATCH net-next v2 0/6] net: ipa: simplify IPA interrupt handling Alex Elder
2023-01-04 17:52 ` [PATCH net-next v2 1/6] net: ipa: introduce a common microcontroller interrupt handler Alex Elder
2023-01-04 17:52 ` [PATCH net-next v2 2/6] net: ipa: introduce ipa_interrupt_enable() Alex Elder
2023-01-04 17:52 ` [PATCH net-next v2 3/6] net: ipa: enable IPA interrupt handlers separate from registration Alex Elder
2023-01-04 17:52 ` [PATCH net-next v2 4/6] net: ipa: register IPA interrupt handlers directly Alex Elder
2023-01-04 17:52 ` [PATCH net-next v2 5/6] net: ipa: kill ipa_interrupt_add() Alex Elder
2023-01-04 17:52 ` [PATCH net-next v2 6/6] net: ipa: don't maintain IPA interrupt handler array Alex Elder
2023-01-06 6:10 ` [PATCH net-next v2 0/6] net: ipa: simplify IPA interrupt handling patchwork-bot+netdevbpf
2023-01-06 6:17 ` Jakub Kicinski [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=20230105221708.659069f1@kernel.org \
--to=kuba@kernel.org \
--cc=andersson@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.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=patchwork-bot+netdevbpf@kernel.org \
--cc=quic_avuyyuru@quicinc.com \
--cc=quic_cpratapa@quicinc.com \
--cc=quic_jponduru@quicinc.com \
--cc=quic_subashab@quicinc.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).