From: Roopa Prabhu <roopa@nvidia.com>
To: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>,
netdev@vger.kernel.org
Cc: outreachy@lists.linux.dev, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: vxlan: Fix kernel coding style
Date: Thu, 19 May 2022 22:06:53 -0700 [thread overview]
Message-ID: <7dbf218e-1a9a-13a4-6b6f-0e23899fb1cb@nvidia.com> (raw)
In-Reply-To: <20220520003614.6073-1-eng.alaamohamedsoliman.am@gmail.com>
On 5/19/22 17:36, Alaa Mohamed wrote:
> The continuation line does not align with the opening bracket
> and this patch fix it.
>
> Signed-off-by: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>
> ---
> changes in v2:
> fix the alignment of the "DST, VNI, ifindex and port are mutually exclusive with NH_ID"
> string to the open parenthesis of the NL_SET_ERR_MSG macro in vxlan_fdb_parse().
> ---
> drivers/net/vxlan/vxlan_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/vxlan/vxlan_core.c b/drivers/net/vxlan/vxlan_core.c
> index 293082c32a78..29db08f15e38 100644
> --- a/drivers/net/vxlan/vxlan_core.c
> +++ b/drivers/net/vxlan/vxlan_core.c
> @@ -1138,7 +1138,7 @@ static int vxlan_fdb_parse(struct nlattr *tb[], struct vxlan_dev *vxlan,
> if (tb[NDA_NH_ID] && (tb[NDA_DST] || tb[NDA_VNI] || tb[NDA_IFINDEX] ||
> tb[NDA_PORT])) {
> NL_SET_ERR_MSG(extack,
> - "DST, VNI, ifindex and port are mutually exclusive with NH_ID");
> + "DST, VNI, ifindex and port are mutually exclusive with NH_ID");
it looks still off by a space.
> return -EINVAL;
> }
this closing brace should line up with the if
>
> @@ -1297,7 +1297,7 @@ int __vxlan_fdb_delete(struct vxlan_dev *vxlan,
> static int vxlan_fdb_delete(struct ndmsg *ndm, struct nlattr *tb[],
> struct net_device *dev,
> const unsigned char *addr, u16 vid,
> - struct netlink_ext_ack *extack)
> + struct netlink_ext_ack *extack)
> {
> struct vxlan_dev *vxlan = netdev_priv(dev);
> union vxlan_addr ip;
next prev parent reply other threads:[~2022-05-20 5:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 0:36 Alaa Mohamed
2022-05-20 5:06 ` Roopa Prabhu [this message]
2022-05-21 0:40 ` Jakub Kicinski
2022-05-24 0:10 ` Roopa Prabhu
2022-05-21 0:50 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-05-20 0:24 Alaa Mohamed
2022-05-20 0:14 Alaa Mohamed
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=7dbf218e-1a9a-13a4-6b6f-0e23899fb1cb@nvidia.com \
--to=roopa@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eng.alaamohamedsoliman.am@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®