public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Baruch Siach <baruch@tkos•co.il>
Cc: alexandre.torgue@foss•st.com, joabreu@synopsys•com,
	netdev@vger•kernel.org, fancer.lancer@gmail•com,
	pabeni@redhat•com
Subject: Re: [PATCH net-next v3 1/2] net: stmmac: remove extra newline from descriptors display
Date: Tue, 21 Nov 2023 11:50:22 +0000	[thread overview]
Message-ID: <170056742265.32090.5713757301002366239.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <444f3b1dd409fdb14ed2a1ae7679a86b110dadcd.1700372381.git.baruch@tkos.co.il>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat•com>:

On Sun, 19 Nov 2023 07:39:40 +0200 you wrote:
> One newline per line should be enough. Reduce the verbosity of
> descriptors dump.
> 
> Reviewed-by: Serge Semin <fancer.lancer@gmail•com>
> Signed-off-by: Baruch Siach <baruch@tkos•co.il>
> ---
>  drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 1 -
>  1 file changed, 1 deletion(-)

Here is the summary with links:
  - [net-next,v3,1/2] net: stmmac: remove extra newline from descriptors display
    https://git.kernel.org/netdev/net-next/c/7911deba293d
  - [net-next,v3,2/2] net: stmmac: reduce dma ring display code duplication
    https://git.kernel.org/netdev/net-next/c/79a4f4dfa69a

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



      parent reply	other threads:[~2023-11-21 11:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19  5:39 [PATCH net-next v3 1/2] net: stmmac: remove extra newline from descriptors display Baruch Siach
2023-11-19  5:39 ` [PATCH net-next v3 2/2] net: stmmac: reduce dma ring display code duplication Baruch Siach
2023-11-21 11:50 ` 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=170056742265.32090.5713757301002366239.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=alexandre.torgue@foss$(echo .)st.com \
    --cc=baruch@tkos$(echo .)co.il \
    --cc=fancer.lancer@gmail$(echo .)com \
    --cc=joabreu@synopsys$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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