public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, evgreen@chromium.org,
	subashab@codeaurora.org, cpratapa@codeaurora.org,
	bjorn.andersson@linaro.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] net: ipa: GSI register consolidation
Date: Fri, 13 Nov 2020 23:20:05 +0000	[thread overview]
Message-ID: <160530960571.2715.16368912876962329757.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201110215922.23514-1-elder@linaro.org>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Tue, 10 Nov 2020 15:59:16 -0600 you wrote:
> This series rearranges and consolidates some GSI register
> definitions.  Its general aim is to make things more
> consistent, by:
>   - Using enumerated types to define the values held in GSI register
>     fields
>   - Defining field values in "gsi_reg.h", together with the
>     definition of the register (and field) that holds them
>   - Format enumerated type members consistently, with hexidecimal
>     numeric values, and assignments aligned on the same column
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] net: ipa: define GSI interrupt types with enums
    https://git.kernel.org/netdev/net-next/c/6c6358cca6fd
  - [net-next,2/6] net: ipa: use common value for channel type and protocol
    https://git.kernel.org/netdev/net-next/c/46dda53ef7de
  - [net-next,3/6] net: ipa: move channel type values into "gsi_reg.h"
    https://git.kernel.org/netdev/net-next/c/9ed8c2a92d01
  - [net-next,4/6] net: ipa: move GSI error values into "gsi_reg.h"
    https://git.kernel.org/netdev/net-next/c/7b0ac8f65116
  - [net-next,5/6] net: ipa: move GSI command opcode values into "gsi_reg.h"
    https://git.kernel.org/netdev/net-next/c/cec2076e432e
  - [net-next,6/6] net: ipa: use enumerated types for GSI field values
    https://git.kernel.org/netdev/net-next/c/4730ab1c1d27

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2020-11-13 23:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 21:59 [PATCH net-next 0/6] net: ipa: GSI register consolidation Alex Elder
2020-11-10 21:59 ` [PATCH net-next 1/6] net: ipa: define GSI interrupt types with enums Alex Elder
2020-11-10 21:59 ` [PATCH net-next 2/6] net: ipa: use common value for channel type and protocol Alex Elder
2020-11-10 21:59 ` [PATCH net-next 3/6] net: ipa: move channel type values into "gsi_reg.h" Alex Elder
2020-11-10 21:59 ` [PATCH net-next 4/6] net: ipa: move GSI error " Alex Elder
2020-11-10 21:59 ` [PATCH net-next 5/6] net: ipa: move GSI command opcode " Alex Elder
2020-11-10 21:59 ` [PATCH net-next 6/6] net: ipa: use enumerated types for GSI field values Alex Elder
2020-11-13 23:20 ` patchwork-bot+netdevbpf [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=160530960571.2715.16368912876962329757.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=cpratapa@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=elder@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=subashab@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox