From: yuan linyu <cugyly@163.com>
To: 吉藤英明 <hideaki.yoshifuji@miraclelinux.com>
Cc: network dev <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Joe Perches <joe@perches.com>, David Ahern <dsahern@gmail.com>,
yuan linyu <Linyu.Yuan@alcatel-sbell.com.cn>,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH net-next 1/2] net: ndisc.c: fix coding style issue
Date: Fri, 26 May 2017 21:55:32 +0800 [thread overview]
Message-ID: <1495806932.5755.4.camel@163.com> (raw)
In-Reply-To: <CAPA1RqDqyZicNWM8arSvMfQjmy_A=LLEjtTwH8KTza4WwQ_dsg@mail.gmail.com>
On 五, 2017-05-26 at 22:45 +0900, 吉藤英明 wrote:
> Hi,
>
> 2017-05-26 22:23 GMT+09:00 yuan linyu <cugyly@163.com>:
> >
> > From: yuan linyu <Linyu.Yuan@alcatel-sbell.com.cn>
> >
> > Signed-off-by: yuan linyu <Linyu.Yuan@alcatel-sbell.com.cn>
> > ---
> > net/ipv6/ndisc.c | 109 ++++++++++++++++++++++++++++---------------------------
> > 1 file changed, 55 insertions(+), 54 deletions(-)
> Sorry, I don't think this kind of change for style is good
> bacause this makes effort of backport more difficult.
hi, i can't understand.
if any change of this code you decide to backport, it need effort,
not only important fix.
do I miss your point ?
>
> --yoshfuji
>
next prev parent reply other threads:[~2017-05-26 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 13:23 [PATCH net-next 1/2] net: ndisc.c: fix coding style issue yuan linyu
2017-05-26 13:45 ` 吉藤英明
2017-05-26 13:55 ` yuan linyu [this message]
2017-05-26 17:25 ` 吉藤英明
2017-05-26 22:08 ` yuan linyu
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=1495806932.5755.4.camel@163.com \
--to=cugyly@163.com \
--cc=Linyu.Yuan@alcatel-sbell.com.cn \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).