netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Weihang Li <liweihang@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	linuxarm@huawei.com
Subject: Re: [PATCH net-next 0/7] net: fix some coding style issues
Date: Wed, 31 Mar 2021 21:50:09 +0000	[thread overview]
Message-ID: <161722740960.23154.3629056358879323696.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1617178714-14031-1-git-send-email-liweihang@huawei.com>

Hello:

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

On Wed, 31 Mar 2021 16:18:27 +0800 you wrote:
> Do some cleanups according to the coding style of kernel, including wrong
> print type, redundant and missing spaces and so on.
> 
> Yangyang Li (1):
>   net: lpc_eth: fix format warnings of block comments
> 
> Yixing Liu (6):
>   net: ena: fix inaccurate print type
>   net: ena: remove extra words from comments
>   net: amd8111e: fix inappropriate spaces
>   net: amd: correct some format issues
>   net: ocelot: fix a trailling format issue with block comments
>   net: toshiba: fix the trailing format of some block comments
> 
> [...]

Here is the summary with links:
  - [net-next,1/7] net: ena: fix inaccurate print type
    https://git.kernel.org/netdev/net-next/c/b788ff0a7d7d
  - [net-next,2/7] net: ena: remove extra words from comments
    https://git.kernel.org/netdev/net-next/c/e355fa6a3f40
  - [net-next,3/7] net: amd8111e: fix inappropriate spaces
    https://git.kernel.org/netdev/net-next/c/ca3fc0aa0837
  - [net-next,4/7] net: amd: correct some format issues
    https://git.kernel.org/netdev/net-next/c/3f6ebcffaf67
  - [net-next,5/7] net: ocelot: fix a trailling format issue with block comments
    https://git.kernel.org/netdev/net-next/c/1f78ff4ff708
  - [net-next,6/7] net: toshiba: fix the trailing format of some block comments
    https://git.kernel.org/netdev/net-next/c/142c1d2ed966
  - [net-next,7/7] net: lpc_eth: fix format warnings of block comments
    https://git.kernel.org/netdev/net-next/c/44d043b53d38

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



      parent reply	other threads:[~2021-03-31 21:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31  8:18 [PATCH net-next 0/7] net: fix some coding style issues Weihang Li
2021-03-31  8:18 ` [PATCH net-next 1/7] net: ena: fix inaccurate print type Weihang Li
2021-03-31  8:18 ` [PATCH net-next 2/7] net: ena: remove extra words from comments Weihang Li
2021-03-31  8:18 ` [PATCH net-next 3/7] net: amd8111e: fix inappropriate spaces Weihang Li
2021-03-31  8:18 ` [PATCH net-next 4/7] net: amd: correct some format issues Weihang Li
2021-03-31  8:18 ` [PATCH net-next 5/7] net: ocelot: fix a trailling format issue with block comments Weihang Li
2021-03-31  8:18 ` [PATCH net-next 6/7] net: toshiba: fix the trailing format of some " Weihang Li
2021-03-31  8:18 ` [PATCH net-next 7/7] net: lpc_eth: fix format warnings of " Weihang Li
2021-03-31 21: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=161722740960.23154.3629056358879323696.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liweihang@huawei.com \
    --cc=netdev@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 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).