From: patchwork-bot+netdevbpf@kernel.org
To: Lijun Pan <lijunp213@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/8] a set of fixes of coding style
Date: Thu, 11 Feb 2021 21:10:10 +0000 [thread overview]
Message-ID: <161307781002.4804.7034883194654161142.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210211064325.80591-1-lijunp213@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 11 Feb 2021 00:43:17 -0600 you wrote:
> This series address several coding style problems.
>
> v2: rebased on top of tree. Add the Reviewed-by tag from v1 reviews.
> patch 8/8 is new.
>
> Lijun Pan (8):
> ibmvnic: prefer 'unsigned long' over 'unsigned long int'
> ibmvnic: fix block comments
> ibmvnic: fix braces
> ibmvnic: avoid multiple line dereference
> ibmvnic: fix miscellaneous checks
> ibmvnic: add comments for spinlock_t definitions
> ibmvnic: remove unused spinlock_t stats_lock definition
> ibmvnic: prefer strscpy over strlcpy
>
> [...]
Here is the summary with links:
- [net-next,v2,1/8] ibmvnic: prefer 'unsigned long' over 'unsigned long int'
https://git.kernel.org/netdev/net-next/c/429aa36469f9
- [net-next,v2,2/8] ibmvnic: fix block comments
https://git.kernel.org/netdev/net-next/c/bab08bedcdc3
- [net-next,v2,3/8] ibmvnic: fix braces
https://git.kernel.org/netdev/net-next/c/f78afaace636
- [net-next,v2,4/8] ibmvnic: avoid multiple line dereference
https://git.kernel.org/netdev/net-next/c/914789acaaae
- [net-next,v2,5/8] ibmvnic: fix miscellaneous checks
https://git.kernel.org/netdev/net-next/c/91dc5d2553fb
- [net-next,v2,6/8] ibmvnic: add comments for spinlock_t definitions
https://git.kernel.org/netdev/net-next/c/a369d96ca554
- [net-next,v2,7/8] ibmvnic: remove unused spinlock_t stats_lock definition
https://git.kernel.org/netdev/net-next/c/4bb9f2e48299
- [net-next,v2,8/8] ibmvnic: prefer strscpy over strlcpy
https://git.kernel.org/netdev/net-next/c/8a96c80e2774
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-02-11 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 6:43 [PATCH net-next v2 0/8] a set of fixes of coding style Lijun Pan
2021-02-11 6:43 ` [PATCH net-next v2 1/8] ibmvnic: prefer 'unsigned long' over 'unsigned long int' Lijun Pan
2021-02-11 6:43 ` [PATCH net-next v2 2/8] ibmvnic: fix block comments Lijun Pan
2021-02-11 6:43 ` [PATCH net-next v2 3/8] ibmvnic: fix braces Lijun Pan
2021-02-11 6:43 ` [PATCH net-next v2 4/8] ibmvnic: avoid multiple line dereference Lijun Pan
2021-02-11 6:43 ` [PATCH net-next v2 5/8] ibmvnic: fix miscellaneous checks Lijun Pan
2021-02-11 6:43 ` [PATCH net-next v2 6/8] ibmvnic: add comments for spinlock_t definitions Lijun Pan
2021-02-11 6:43 ` [PATCH net-next v2 7/8] ibmvnic: remove unused spinlock_t stats_lock definition Lijun Pan
2021-02-11 6:43 ` [PATCH net-next v2 8/8] ibmvnic: prefer strscpy over strlcpy Lijun Pan
2021-02-11 21:10 ` 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=161307781002.4804.7034883194654161142.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=lijunp213@gmail.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).