| Message ID | 50AD9351.5020805@asianux.com |
|---|---|
| State | RFC, archived |
| Delegated to: | David Miller |
| Headers | show |
Hi chen gang: For length of device name which less than 8 char， your patch changes them to be print from align right to align left. But at least since 2005(git age-time), we keep this style so far. Maybe, since birth of this code, just align right. :-) Why we *should* change this style? just keep be consistent with the case which length of device name greater than 8 char? Not only old name rule i.e. eth0,eth1, but also new name rule base on pci address ,i.e. em1,p3p1. most of them are less than 8 char. Should not we take more attention on the case less than 8 char? By addition, if we want to add new field in the future, align right is a better choice. Chen Gang said, at 2012/11/22 10:52: > Hi Shan Wei, Eric Dumazet > > is this patch integrated into main branch ? > if need me for additional completion (such as: merge another 2 trivial patches into this patch, too) > please tell me, I will do. > > I understand you are working overtime, maybe no time for any minor and trivial patches. > if surely it is, I think: > you can modify these code manually, and obsolete these minor and trivial patches which I provided. > I do not mind whether mention me in another new patches (you can mention me or not mention me, both are OK). > since our goal is to provide contributes to outside, efficiently. > > regards > > gchen > > > 于 2012年11月05日 11:02, Chen Gang 写道: >> >> 1. not to send same patch triple times. > > thanks, I shall notice, next time. > (I shall 'believe' another members). > >> 2. config your email client,because tab is changed to space. >> you can read Documentation/email-clients.txt. > > 1) thanks. I shall notice, next time. > 2) now, I get gvim as extention editor for thounderbird > 3) the patch is generated by `git format-patch -s --summary --stat` > it use "' '\t" as head, I do not touch it, maybe it is correct. > > welcome any members to giving additional suggestions and completions. > > thanks > > the modified contents are below, > ----------------------------------------------------------------------------------- > > the length of rt->dst.dev->name is 16 (IFNAMSIZ) > in seq_printf, it is not suitable to use %8s for rt->dst.dev->name. > so change it to %s, since each line has not been solid any more. > > additional information: > > %8s limit the width, not for the original string output length > if name length is more than 8, it still can be fully displayed. > if name length is less than 8, the ' ' will be filled before name. > > %.8s truly limit the original string output length (precision) > > Signed-off-by: Chen Gang <gang.chen@asianux.com> > --- > net/ipv6/route.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/net/ipv6/route.c b/net/ipv6/route.c > index c42650c..b60bc52 100644 > --- a/net/ipv6/route.c > +++ b/net/ipv6/route.c > @@ -2835,7 +2835,7 @@ static int rt6_info_route(struct rt6_info *rt, void *p_arg) > } else { > seq_puts(m, "00000000000000000000000000000000"); > } > - seq_printf(m, " %08x %08x %08x %08x %8s\n", > + seq_printf(m, " %08x %08x %08x %08x %s\n", > rt->rt6i_metric, atomic_read(&rt->dst.__refcnt), > rt->dst.__use, rt->rt6i_flags, > rt->dst.dev ? rt->dst.dev->name : ""); > > > -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
于 2012年11月22日 13:28, Shan Wei 写道: > Hi chen gang: > > For length of device name which less than 8 char， > your patch changes them to be print from align right > to align left. But at least since 2005(git age-time), > we keep this style so far. > Maybe, since birth of this code, just align right. :-) > originally, it is a solid output length, the length is "#define RT6_INFO_LEN (32 + 4 + 32 + 4 + 32 + 40 + 5 + 1)" and RHEL5 (kernel-2.6.18-308.20.el5) still use it. it assume that the length of rt->rt6i_dev->name (in RHEL5) is 8. > Why we *should* change this style? > just keep be consistent with the case which length of device > name greater than 8 char? > as a solid length, 8 is not suitable, firstly I suggest to '%16s' (I call it 'beautiful', but for RHEL5, it is a correctness issue) and Eric Dumazet suggest use '%s' is better, since it is not solid length any more (have already let seq_printf instead of arg->buffer) and I think: as a result, what he said is reasonable > Not only old name rule i.e. eth0,eth1, but also new name rule > base on pci address ,i.e. em1,p3p1. most of them are less than 8 char. > Should not we take more attention on the case less than 8 char? > I have ever seen such a device name is more than 8 characters. I am not quite sure: maybe they are eth-route* or eth-usb* ... I will check it in these days, please wait for some days. > By addition, if we want to add new field in the future, > align right is a better choice. > maybe what you said is better (still keep it 'beautiful', but need use '%16s' instead of '%8s') for this, Eric Dumazet maybe have his opinions. Regards gchen. > > Chen Gang said, at 2012/11/22 10:52: >> Hi Shan Wei, Eric Dumazet >> >> is this patch integrated into main branch ? >> if need me for additional completion (such as: merge another 2 trivial patches into this patch, too) >> please tell me, I will do. >> >> I understand you are working overtime, maybe no time for any minor and trivial patches. >> if surely it is, I think: >> you can modify these code manually, and obsolete these minor and trivial patches which I provided. >> I do not mind whether mention me in another new patches (you can mention me or not mention me, both are OK). >> since our goal is to provide contributes to outside, efficiently. >> >> regards >> >> gchen >> >> >> 于 2012年11月05日 11:02, Chen Gang 写道: >>> >>> 1. not to send same patch triple times. >> >> thanks, I shall notice, next time. >> (I shall 'believe' another members). >> >>> 2. config your email client,because tab is changed to space. >>> you can read Documentation/email-clients.txt. >> >> 1) thanks. I shall notice, next time. >> 2) now, I get gvim as extention editor for thounderbird >> 3) the patch is generated by `git format-patch -s --summary --stat` >> it use "' '\t" as head, I do not touch it, maybe it is correct. >> >> welcome any members to giving additional suggestions and completions. >> >> thanks >> >> the modified contents are below, >> ----------------------------------------------------------------------------------- >> >> the length of rt->dst.dev->name is 16 (IFNAMSIZ) >> in seq_printf, it is not suitable to use %8s for rt->dst.dev->name. >> so change it to %s, since each line has not been solid any more. >> >> additional information: >> >> %8s limit the width, not for the original string output length >> if name length is more than 8, it still can be fully displayed. >> if name length is less than 8, the ' ' will be filled before name. >> >> %.8s truly limit the original string output length (precision) >> >> Signed-off-by: Chen Gang <gang.chen@asianux.com> >> --- >> net/ipv6/route.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/net/ipv6/route.c b/net/ipv6/route.c >> index c42650c..b60bc52 100644 >> --- a/net/ipv6/route.c >> +++ b/net/ipv6/route.c >> @@ -2835,7 +2835,7 @@ static int rt6_info_route(struct rt6_info *rt, void *p_arg) >> } else { >> seq_puts(m, "00000000000000000000000000000000"); >> } >> - seq_printf(m, " %08x %08x %08x %08x %8s\n", >> + seq_printf(m, " %08x %08x %08x %08x %s\n", >> rt->rt6i_metric, atomic_read(&rt->dst.__refcnt), >> rt->dst.__use, rt->rt6i_flags, >> rt->dst.dev ? rt->dst.dev->name : ""); >> >> >> > > >
1) about the proof:
currently, sorry for I can not find the device which name length is more than 8.
maybe they (Asianux user) use system call in user mode to assign the new name to device.
please reference: dev_ioctl -> dev_ifsioc -> dev_change_name in net/core/dev.c.
I do not know why they want to change the net device name (but they surely can do).
2) about %*s:
since kernel is an open system, IFNAMSIZ is belong to OS API level for outside
it has effect both on individual kernel modules and user mode system call
we need obey this rule, and %8s is not match this rule.
so %8s is not suitable. (and now we have to choose %16s or %s).
for the format of information which seq_printf output:
it is not belong to OS API level for outside (at least, for current case, it is true).
so we need not keep 'compatible' of it, so %16s is not necessary.
for keeping source code simple and clearly:
%s is better than %16s.
so for result, we should choose %s only (neither %16s nor %8s).
3) about my original mail:
why did my original mail (first mail relative with this patch) say %16s ?
my goals are:
i) to confirm whether suitable to communicate about RHEL* in *@vger.kernel.org.
ii) to confirm whether *@vger.kernel.org welcome such a minor patch (at least, it is not a spam).
iii) to confirm whether *@vger.kernel.org are focused on coding.
(so I intended to use %16s and 'beautiful')
(I have seen too many another various organizations to not be focused on coding)
after get feed back from Eric Dumazet.
i) it is not suitable to communicate about RHEL* in *@vger.kernel.org.
ii) *@vger.kernel.org welcome such a minor patch.
iii) *@vger.kernel.org are focused on coding.
(so I am sure that can use "coding review" to provide contributes to *@vger.kernel.org)
Regards
gchen.
-------- 原始消息 --------
主题: Re: [PATCH] net: ipv6: change %8s to %s for rt->dst.dev->name in seq_printf of rt6_info_route
日期: Thu, 22 Nov 2012 16:37:27 +0800
发件人: Chen Gang <gang.chen@asianux.com>
收件人: Shan Wei <shanwei88@gmail.com>
抄送: Eric Dumazet <eric.dumazet@gmail.com>, David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
于 2012年11月22日 13:28, Shan Wei 写道:
> Hi chen gang:
>
> For length of device name which less than 8 char，
> your patch changes them to be print from align right
> to align left. But at least since 2005(git age-time),
> we keep this style so far.
> Maybe, since birth of this code, just align right. :-)
>
originally, it is a solid output length, the length is "#define
RT6_INFO_LEN (32 + 4 + 32 + 4 + 32 + 40 + 5 + 1)"
and RHEL5 (kernel-2.6.18-308.20.el5) still use it.
it assume that the length of rt->rt6i_dev->name (in RHEL5) is 8.
> Why we *should* change this style?
> just keep be consistent with the case which length of device
> name greater than 8 char?
>
as a solid length, 8 is not suitable, firstly I suggest to '%16s' (I
call it 'beautiful', but for RHEL5, it is a correctness issue)
and Eric Dumazet suggest use '%s' is better, since it is not solid
length any more (have already let seq_printf instead of arg->buffer)
and I think: as a result, what he said is reasonable
> Not only old name rule i.e. eth0,eth1, but also new name rule
> base on pci address ,i.e. em1,p3p1. most of them are less than 8 char.
> Should not we take more attention on the case less than 8 char?
>
I have ever seen such a device name is more than 8 characters.
I am not quite sure: maybe they are eth-route* or eth-usb* ...
I will check it in these days, please wait for some days.
> By addition, if we want to add new field in the future,
> align right is a better choice.
>
maybe what you said is better (still keep it 'beautiful', but need use
'%16s' instead of '%8s')
for this, Eric Dumazet maybe have his opinions.
Regards
gchen.
>
> Chen Gang said, at 2012/11/22 10:52:
>> Hi Shan Wei, Eric Dumazet
>>
>> is this patch integrated into main branch ?
>> if need me for additional completion (such as: merge another 2 trivial patches into this patch, too)
>> please tell me, I will do.
>>
>> I understand you are working overtime, maybe no time for any minor and trivial patches.
>> if surely it is, I think:
>> you can modify these code manually, and obsolete these minor and trivial patches which I provided.
>> I do not mind whether mention me in another new patches (you can mention me or not mention me, both are OK).
>> since our goal is to provide contributes to outside, efficiently.
>>
>> regards
>>
>> gchen
>>
>>
>> 于 2012年11月05日 11:02, Chen Gang 写道:
>>>
>>> 1. not to send same patch triple times.
>>
>> thanks, I shall notice, next time.
>> (I shall 'believe' another members).
>>
>>> 2. config your email client,because tab is changed to space.
>>> you can read Documentation/email-clients.txt.
>>
>> 1) thanks. I shall notice, next time.
>> 2) now, I get gvim as extention editor for thounderbird
>> 3) the patch is generated by `git format-patch -s --summary --stat`
>> it use "' '\t" as head, I do not touch it, maybe it is correct.
>>
>> welcome any members to giving additional suggestions and completions.
>>
>> thanks
>>
>> the modified contents are below,
>> -----------------------------------------------------------------------------------
>>
>> the length of rt->dst.dev->name is 16 (IFNAMSIZ)
>> in seq_printf, it is not suitable to use %8s for rt->dst.dev->name.
>> so change it to %s, since each line has not been solid any more.
>>
>> additional information:
>>
>> %8s limit the width, not for the original string output length
>> if name length is more than 8, it still can be fully displayed.
>> if name length is less than 8, the ' ' will be filled before name.
>>
>> %.8s truly limit the original string output length (precision)
>>
>> Signed-off-by: Chen Gang <gang.chen@asianux.com>
>> ---
>> net/ipv6/route.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
>> index c42650c..b60bc52 100644
>> --- a/net/ipv6/route.c
>> +++ b/net/ipv6/route.c
>> @@ -2835,7 +2835,7 @@ static int rt6_info_route(struct rt6_info *rt, void *p_arg)
>> } else {
>> seq_puts(m, "00000000000000000000000000000000");
>> }
>> - seq_printf(m, " %08x %08x %08x %08x %8s\n",
>> + seq_printf(m, " %08x %08x %08x %08x %s\n",
>> rt->rt6i_metric, atomic_read(&rt->dst.__refcnt),
>> rt->dst.__use, rt->rt6i_flags,
>> rt->dst.dev ? rt->dst.dev->name : "");
>>
>>
>>
>
>
>
Chen Gang said, at 2012/11/23 11:35: > 2) about %*s: > since kernel is an open system, IFNAMSIZ is belong to OS API level for outside > it has effect both on individual kernel modules and user mode system call > we need obey this rule, and %8s is not match this rule. > so %8s is not suitable. (and now we have to choose %16s or %s). Your patch will change the format of /proc/net/ipv6_route. Why we need to keep be consistent with user mode? However user operates device name, no effect on the showing of /proc/net/ipv6_route. > > for the format of information which seq_printf output: > it is not belong to OS API level for outside (at least, for current case, it is true). > so we need not keep 'compatible' of it, so %16s is not necessary. Can you explain If we don't change to %s, what will happen? > > for keeping source code simple and clearly: > %s is better than %16s. > > so for result, we should choose %s only (neither %16s nor %8s). -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
于 2012年11月27日 11:17, Shan Wei 写道: > Chen Gang said, at 2012/11/23 11:35: >> 2) about %*s: >> since kernel is an open system, IFNAMSIZ is belong to OS API level for outside >> it has effect both on individual kernel modules and user mode system call >> we need obey this rule, and %8s is not match this rule. >> so %8s is not suitable. (and now we have to choose %16s or %s). > > Your patch will change the format of /proc/net/ipv6_route. Yes, it will be changed. although it belongs to "User Experience", it is not belong to os api level. for os api level: we must commit them not be changed (they are testament) for User Experience: we can change it, but maybe users feel 'not good'. > Why we need to keep be consistent with user mode? it is for "keep source code simple and clear" when others see the %8s, easy to make them miss understanding (not quite clear) so better to change it to %s. > However user operates device name, no effect on the showing of /proc/net/ipv6_route. now, no effect. all together: since we are not user interactive program, "keeping source code simple and clear" is more important than "User Experience" > >> >> for the format of information which seq_printf output: >> it is not belong to OS API level for outside (at least, for current case, it is true). >> so we need not keep 'compatible' of it, so %16s is not necessary. > > Can you explain If we don't change to %s, what will happen? > for outside, nothing will happen. so it is not for correctness, it is only for "keep source code simple and clear". >> >> for keeping source code simple and clearly: >> %s is better than %16s. >> >> so for result, we should choose %s only (neither %16s nor %8s). > > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > >
于 2012年11月27日 12:18, Chen Gang 写道: > 于 2012年11月27日 11:17, Shan Wei 写道: >> > Chen Gang said, at 2012/11/23 11:35: >>> >> 2) about %*s: >>> >> since kernel is an open system, IFNAMSIZ is belong to OS API level for outside >>> >> it has effect both on individual kernel modules and user mode system call >>> >> we need obey this rule, and %8s is not match this rule. >>> >> so %8s is not suitable. (and now we have to choose %16s or %s). >> > >> > Your patch will change the format of /proc/net/ipv6_route. > Yes, it will be changed. > although it belongs to "User Experience", it is not belong to os api level. > for os api level: we must commit them not be changed (they are testament) > for User Experience: we can change it, but maybe users feel 'not good'. > I think (only for my thought, maybe not correct): for user input through /proc/* are all for os api level, not for "User Experience". for most of outputs to user through /proc/*, are "User Experience". >> > Why we need to keep be consistent with user mode? > it is for "keep source code simple and clear" > when others see the %8s, easy to make them miss understanding (not quite clear) > so better to change it to %s. > > >> > However user operates device name, no effect on the showing of /proc/net/ipv6_route. > now, no effect. > > > all together: > since we are not user interactive program, > "keeping source code simple and clear" is more important than "User Experience" > > >> > >>> >> >>> >> for the format of information which seq_printf output: >>> >> it is not belong to OS API level for outside (at least, for current case, it is true). >>> >> so we need not keep 'compatible' of it, so %16s is not necessary. >> > >> > Can you explain If we don't change to %s, what will happen? >> > > for outside, nothing will happen. > > so it is not for correctness, it is only for "keep source code simple and clear". > >>> >> >>> >> for keeping source code simple and clearly: >>> >> %s is better than %16s. >>> >> >>> >> so for result, we should choose %s only (neither %16s nor %8s). >> > >> > -- >> > To unsubscribe from this list: send the line "unsubscribe netdev" in >> > the body of a message to majordomo@vger.kernel.org >> > More majordomo info at http://vger.kernel.org/majordomo-info.html >> > >> > > > -- Chen Gang Asianux Corporation -- To unsubscribe from this list: send > the line "unsubscribe netdev" in the body of a message to > majordomo@vger.kernel.org More majordomo info at > http://vger.kernel.org/majordomo-info.html >
Chen Gang said, at 2012/11/27 12:18: >> >>> >>> for the format of information which seq_printf output: >>> it is not belong to OS API level for outside (at least, for current case, it is true). >>> so we need not keep 'compatible' of it, so %16s is not necessary. >> >> Can you explain If we don't change to %s, what will happen? >> > > for outside, nothing will happen. > > so it is not for correctness, it is only for "keep source code simple and clear". So, it's a clean-up type patch which is just for developer, but with the change of /proc interface which is for user. user is first, so let us end this thread unless you have necessary reasons to do it. Thanks Shan Wei -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
于 2012年11月27日 12:56, Shan Wei 写道: > Chen Gang said, at 2012/11/27 12:18: >>> >>>> >>>> for the format of information which seq_printf output: >>>> it is not belong to OS API level for outside (at least, for current case, it is true). >>>> so we need not keep 'compatible' of it, so %16s is not necessary. >>> >>> Can you explain If we don't change to %s, what will happen? >>> >> >> for outside, nothing will happen. >> >> so it is not for correctness, it is only for "keep source code simple and clear". > > So, it's a clean-up type patch which is just for developer, > but with the change of /proc interface which is for user. > user is first, so let us end this thread unless you have necessary reasons to do it. > 1) it is not change the /proc interface. a) both %8s and %s do not change the output interface format (including contents, topology, separator mark, space redundancy). b) it is belong to 'User Experience', not belong to os api. c) do you agree with what I say above ? 2) I think: one of the differences between system service and user interactive program are: for system service (including kernel): "clean-up" is more important than "UE". for user interactive program: "UE" is more important than "Clean-up". maybe, it is for ideal world (or maybe it is only in theory). (also maybe what I said above is incorrect) 3) so all together: I can understand if it is not integrated into main branch. it will be better to continue discussing it in ideal world (or in theory), I think it is valuable for learning with each other. :-) thanks. gchen. > Thanks > Shan Wei > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > >
> I think (only for my thought, maybe not correct): > for user input through /proc/* are all for os api level, not for "User Experience". > for most of outputs to user through /proc/*, are "User Experience". > and now I think what I said above is incorrect. and now, I think: A) both input and output through /proc/* are for os api level. B) but both %8s and %s do not change the output interface format (including contents, topology, separator mark, space redundancy). C) so it is belong to 'User Experience', not belong to os api. welcome any another members to giving suggestions and completions. thanks. :-)
于 2012年11月27日 13:40, Chen Gang 写道: > > and now, I think: > A) both input and output through /proc/* are for os api level. > B) but both %8s and %s do not change the output interface format (including contents, topology, separator mark, space redundancy). > C) so it is belong to 'User Experience', not belong to os api. > > welcome any another members to giving suggestions and completions. > > thanks. > > :-) > completion: 8 right alignment is not belong to interface format. if it was belong to interface format, it would cause correctness issue (the name len may be larger than 8). so if "8 right alignment" is belong to os api, it means the api is not correct, need change. :-)
completion: "8 right alignment should not belong to os api level" for api, we need keep as fewer contents as we can. for output format api: "contents"+"topology"+"separator mark"+"space redundancy" are enough. so "8 right alignment" should not belong to api level (it only belongs to "User Experience"). "User Experience" is most likely 'beautiful' !! !-) gchen. 于 2012年11月27日 13:52, Chen Gang 写道: > 于 2012年11月27日 13:40, Chen Gang 写道: >> >> and now, I think: >> A) both input and output through /proc/* are for os api level. >> B) but both %8s and %s do not change the output interface format (including contents, topology, separator mark, space redundancy). >> C) so it is belong to 'User Experience', not belong to os api. >> >> welcome any another members to giving suggestions and completions. >> >> thanks. >> >> :-) >> > > completion: 8 right alignment is not belong to interface format. > if it was belong to interface format, > it would cause correctness issue (the name len may be larger than 8). > so if "8 right alignment" is belong to os api, it means the api is not correct, need change. > > :-) >
Hi Shan Wei, Eric, David
maybe what I have done have made negative effect to you.
I am sorry for that, firstly.
excuse me, I am a newbie in *@vger.kernel.org, so not know many things.
also excuse me, my English is not quite well (so at least, not quite gentle)
what I want to do is only to:
provide contributes to outside, without negative effects, base on human resources limitations.
but it seems that I am failed (at least, in net subsystem).
next, I will be careful to continue under another sub systems, and leave net sub system (at least for a while).
sorry again for the negative effects which I made.
Bye.
gchen.
于 2012年11月27日 12:56, Shan Wei 写道:
> Chen Gang said, at 2012/11/27 12:18:
>>>
>>>>
>>>> for the format of information which seq_printf output:
>>>> it is not belong to OS API level for outside (at least, for current case, it is true).
>>>> so we need not keep 'compatible' of it, so %16s is not necessary.
>>>
>>> Can you explain If we don't change to %s, what will happen?
>>>
>>
>> for outside, nothing will happen.
>>
>> so it is not for correctness, it is only for "keep source code simple and clear".
>
> So, it's a clean-up type patch which is just for developer,
> but with the change of /proc interface which is for user.
> user is first, so let us end this thread unless you have necessary reasons to do it.
>
> Thanks
> Shan Wei
>
>
diff --git a/net/ipv6/route.c b/net/ipv6/route.c index c42650c..b60bc52 100644 --- a/net/ipv6/route.c +++ b/net/ipv6/route.c @@ -2835,7 +2835,7 @@ static int rt6_info_route(struct rt6_info *rt, void *p_arg) } else { seq_puts(m, "00000000000000000000000000000000"); } - seq_printf(m, " %08x %08x %08x %08x %8s\n", + seq_printf(m, " %08x %08x %08x %08x %s\n", rt->rt6i_metric, atomic_read(&rt->dst.__refcnt), rt->dst.__use, rt->rt6i_flags, rt->dst.dev ? rt->dst.dev->name : "");
Hi Shan Wei, Eric Dumazet is this patch integrated into main branch ? if need me for additional completion (such as: merge another 2 trivial patches into this patch, too) please tell me, I will do. I understand you are working overtime, maybe no time for any minor and trivial patches. if surely it is, I think: you can modify these code manually, and obsolete these minor and trivial patches which I provided. I do not mind whether mention me in another new patches (you can mention me or not mention me, both are OK). since our goal is to provide contributes to outside, efficiently. regards gchen 于 2012年11月05日 11:02, Chen Gang 写道: > > 1. not to send same patch triple times. thanks, I shall notice, next time. (I shall 'believe' another members). > 2. config your email client,because tab is changed to space. > you can read Documentation/email-clients.txt. 1) thanks. I shall notice, next time. 2) now, I get gvim as extention editor for thounderbird 3) the patch is generated by `git format-patch -s --summary --stat` it use "' '\t" as head, I do not touch it, maybe it is correct. welcome any members to giving additional suggestions and completions. thanks the modified contents are below, ----------------------------------------------------------------------------------- the length of rt->dst.dev->name is 16 (IFNAMSIZ) in seq_printf, it is not suitable to use %8s for rt->dst.dev->name. so change it to %s, since each line has not been solid any more. additional information: %8s limit the width, not for the original string output length if name length is more than 8, it still can be fully displayed. if name length is less than 8, the ' ' will be filled before name. %.8s truly limit the original string output length (precision) Signed-off-by: Chen Gang <gang.chen@asianux.com> --- net/ipv6/route.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html