public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: huangguangbin (A) <huangguangbin2@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, xie.he.0141@gmail.com,
	ms@dev.tdt.de, willemb@google.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, lipeng321@huawei.com,
	tanhuazhong@huawei.com
Subject: Re: [PATCH net-next 0/6] net: hdlc_cisci: clean up some code style issues
Date: Thu, 03 Jun 2021 20:30:04 +0000	[thread overview]
Message-ID: <162275220459.19203.14503519672467316957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1622631676-34037-1-git-send-email-huangguangbin2@huawei.com>

Hello:

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

On Wed, 2 Jun 2021 19:01:10 +0800 you wrote:
> From: Peng Li <lipeng321@huawei.com>
> 
> This patchset clean up some code style issues.
> 
> Peng Li (6):
>   net: hdlc_cisco: remove redundant blank lines
>   net: hdlc_cisco: fix the code style issue about "foo* bar"
>   net: hdlc_cisco: add some required spaces
>   net: hdlc_cisco: remove unnecessary out of memory message
>   net: hdlc_cisco: add blank line after declaration
>   net: hdlc_cisco: remove redundant space
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] net: hdlc_cisco: remove redundant blank lines
    https://git.kernel.org/netdev/net-next/c/5abaf211c4a5
  - [net-next,2/6] net: hdlc_cisco: fix the code style issue about "foo* bar"
    https://git.kernel.org/netdev/net-next/c/001aa274300d
  - [net-next,3/6] net: hdlc_cisco: add some required spaces
    https://git.kernel.org/netdev/net-next/c/c1300f37ea99
  - [net-next,4/6] net: hdlc_cisco: remove unnecessary out of memory message
    https://git.kernel.org/netdev/net-next/c/05ff5525aa82
  - [net-next,5/6] net: hdlc_cisco: add blank line after declaration
    https://git.kernel.org/netdev/net-next/c/4e38d514788c
  - [net-next,6/6] net: hdlc_cisco: remove redundant space
    https://git.kernel.org/netdev/net-next/c/4a20f8ecbf61

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-06-03 20:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 11:01 [PATCH net-next 0/6] net: hdlc_cisci: clean up some code style issues Guangbin Huang
2021-06-02 11:01 ` [PATCH net-next 1/6] net: hdlc_cisco: remove redundant blank lines Guangbin Huang
2021-06-02 11:01 ` [PATCH net-next 2/6] net: hdlc_cisco: fix the code style issue about "foo* bar" Guangbin Huang
2021-06-02 11:01 ` [PATCH net-next 3/6] net: hdlc_cisco: add some required spaces Guangbin Huang
2021-06-02 11:01 ` [PATCH net-next 4/6] net: hdlc_cisco: remove unnecessary out of memory message Guangbin Huang
2021-06-02 11:01 ` [PATCH net-next 5/6] net: hdlc_cisco: add blank line after declaration Guangbin Huang
2021-06-02 11:01 ` [PATCH net-next 6/6] net: hdlc_cisco: remove redundant space Guangbin Huang
2021-06-03 20:30 ` 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=162275220459.19203.14503519672467316957.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=huangguangbin2@huawei.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lipeng321@huawei.com \
    --cc=ms@dev.tdt.de \
    --cc=netdev@vger.kernel.org \
    --cc=tanhuazhong@huawei.com \
    --cc=willemb@google.com \
    --cc=xie.he.0141@gmail.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