From: wangyunjian <wangyunjian@huawei.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xudingke <xudingke@huawei.com>
Subject: RE: [PATCH net-next] tun: Fix code style issues in <linux/if_vlan.h>
Date: Fri, 2 Feb 2024 01:09:10 +0000 [thread overview]
Message-ID: <e59177fbc48944479f0ea4c17fd1c532@huawei.com> (raw)
In-Reply-To: <65bbbc9776ea4_2226992949c@willemb.c.googlers.com.notmuch>
> -----Original Message-----
> From: Willem de Bruijn [mailto:willemdebruijn.kernel@gmail.com]
> Sent: Thursday, February 1, 2024 11:45 PM
> To: wangyunjian <wangyunjian@huawei.com>;
> willemdebruijn.kernel@gmail.com; jasowang@redhat.com; kuba@kernel.org;
> davem@davemloft.net
> Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org; xudingke
> <xudingke@huawei.com>; wangyunjian <wangyunjian@huawei.com>
> Subject: Re: [PATCH net-next] tun: Fix code style issues in <linux/if_vlan.h>
>
> Yunjian Wang wrote:
> > This fixes the following code style problem:
> > - WARNING: please, no spaces at the start of a line
> > - CHECK: Please use a blank line after
> > function/struct/union/enum declarations
> >
> > Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> > ---
> > include/linux/if_tun.h | 16 +++++++++++++---
>
> Subject: s/if_vlan/if_tun/
Yep, my bad, will send v2 with correction.
Thanks
prev parent reply other threads:[~2024-02-02 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 13:23 Yunjian Wang
2024-02-01 15:45 ` Willem de Bruijn
2024-02-02 1:09 ` wangyunjian [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=e59177fbc48944479f0ea4c17fd1c532@huawei.com \
--to=wangyunjian@huawei.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xudingke@huawei.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®