From: Jakub Kicinski <kuba@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: patchwork-bot+netdevbpf@kernel.org, Alex Elder <elder@linaro.org>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
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 00/15] net: ipa: generalized register definitions
Date: Wed, 28 Sep 2022 07:04:21 -0700 [thread overview]
Message-ID: <20220928070421.12b7021a@kernel.org> (raw)
In-Reply-To: <166433041840.32421.1858136173918846349.git-patchwork-notify@kernel.org>
On Wed, 28 Sep 2022 02:00:18 +0000 patchwork-bot+netdevbpf@kernel.org
wrote:
> Hello:
>
> This series was applied to netdev/net-next.git (master)
> by Jakub Kicinski <kuba@kernel.org>:
>
> On Mon, 26 Sep 2022 17:09:16 -0500 you wrote:
> > This series is quite a bit bigger than what I normally like to send,
> > and I apologize for that. I would like it to get incorporated in
> > its entirety this week if possible, and splitting up the series
> > carries a small risk that wouldn't happen.
> >
> > Each IPA register has a defined offset, and in most cases, a set
> > of masks that define the width and position of fields within the
> > register. Most registers currently use the same offset for all
> > versions of IPA. Usually fields within registers are also the same
> > across many versions. Offsets and fields like this are defined
> > using preprocessor constants.
> >
> > [...]
>
> Here is the summary with links:
> - [net-next,01/15] net: ipa: introduce IPA register IDs
> https://git.kernel.org/netdev/net-next/c/98e2dd71a826
> - [net-next,02/15] net: ipa: use IPA register IDs to determine offsets
> https://git.kernel.org/netdev/net-next/c/6bfb753850d3
> - [net-next,03/15] net: ipa: add per-version IPA register definition files
> https://git.kernel.org/netdev/net-next/c/07f120bcf76b
> - [net-next,04/15] net: ipa: use ipa_reg[] array for register offsets
> https://git.kernel.org/netdev/net-next/c/82a06807453a
> - [net-next,05/15] net: ipa: introduce ipa_reg()
> (no matching commit)
> - [net-next,06/15] net: ipa: introduce ipa_reg field masks
> https://git.kernel.org/netdev/net-next/c/a5ad8956f97a
> - [net-next,07/15] net: ipa: define COMP_CFG IPA register fields
> https://git.kernel.org/netdev/net-next/c/12c7ea7dfd2c
> - [net-next,08/15] net: ipa: define CLKON_CFG and ROUTE IPA register fields
> (no matching commit)
> - [net-next,09/15] net: ipa: define some more IPA register fields
> (no matching commit)
> - [net-next,10/15] net: ipa: define more IPA register fields
> (no matching commit)
> - [net-next,11/15] net: ipa: define even more IPA register fields
> (no matching commit)
> - [net-next,12/15] net: ipa: define resource group/type IPA register fields
> (no matching commit)
> - [net-next,13/15] net: ipa: define some IPA endpoint register fields
> (no matching commit)
> - [net-next,14/15] net: ipa: define more IPA endpoint register fields
> (no matching commit)
> - [net-next,15/15] net: ipa: define remaining IPA register fields
> (no matching commit)
>
> You are awesome, thank you!
Hi Konstantin,
did anything change in the pw-bot in the last couple of weeks?
I didn't touch these patches and yet half got missed.
Do you recommend we slap a Link on all patches? Currently I only
add it to the cover letter / merge commit.
prev parent reply other threads:[~2022-09-28 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 22:09 [PATCH net-next 00/15] net: ipa: generalized register definitions Alex Elder
2022-09-26 22:09 ` [PATCH net-next 01/15] net: ipa: introduce IPA register IDs Alex Elder
2022-09-26 22:09 ` [PATCH net-next 02/15] net: ipa: use IPA register IDs to determine offsets Alex Elder
2022-09-26 22:09 ` [PATCH net-next 03/15] net: ipa: add per-version IPA register definition files Alex Elder
2022-09-26 22:09 ` [PATCH net-next 04/15] net: ipa: use ipa_reg[] array for register offsets Alex Elder
2022-09-26 22:09 ` [PATCH net-next 05/15] net: ipa: introduce ipa_reg() Alex Elder
2022-09-26 22:09 ` [PATCH net-next 06/15] net: ipa: introduce ipa_reg field masks Alex Elder
2022-09-26 22:09 ` [PATCH net-next 07/15] net: ipa: define COMP_CFG IPA register fields Alex Elder
2022-09-26 22:09 ` [PATCH net-next 08/15] net: ipa: define CLKON_CFG and ROUTE " Alex Elder
2022-09-26 22:09 ` [PATCH net-next 09/15] net: ipa: define some more " Alex Elder
2022-09-26 22:09 ` [PATCH net-next 10/15] net: ipa: define " Alex Elder
2022-09-26 22:09 ` [PATCH net-next 11/15] net: ipa: define even " Alex Elder
2022-09-26 22:09 ` [PATCH net-next 12/15] net: ipa: define resource group/type " Alex Elder
2022-09-26 22:09 ` [PATCH net-next 13/15] net: ipa: define some IPA endpoint " Alex Elder
2022-09-26 22:09 ` [PATCH net-next 14/15] net: ipa: define more " Alex Elder
2022-09-26 22:09 ` [PATCH net-next 15/15] net: ipa: define remaining IPA " Alex Elder
2022-09-28 2:00 ` [PATCH net-next 00/15] net: ipa: generalized register definitions patchwork-bot+netdevbpf
2022-09-28 14:04 ` 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=20220928070421.12b7021a@kernel.org \
--to=kuba@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=konstantin@linuxfoundation.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).