From: Franko Fang <huananhu@huawei.com>
To: Jarek Poplawski <jarkao2@gmail.com>,
William Allen Simpson <william.allen.simpson@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 17/11]Optimize the upload speed for PPP connection.
Date: Tue, 17 Nov 2009 19:54:43 +0800 [thread overview]
Message-ID: <00b301ca677c$c03f25d0$76900b0a@china.huawei.com> (raw)
In-Reply-To: <20091117111454.GA8341@ff.dom.local>
Well, yes, I think that it misses the tab.
I will update the patch, and resubmit it again.
Thanks for all .
----- Original Message -----
From: "Jarek Poplawski" <jarkao2@gmail.com>
To: "William Allen Simpson" <william.allen.simpson@gmail.com>
Cc: <huananhu@huawei.com>; "David Miller" <davem@davemloft.net>; <netdev@vger.kernel.org>; <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 17, 2009 7:14 PM
Subject: Re: [PATCH 17/11]Optimize the upload speed for PPP connection.
> On 17-11-2009 11:20, William Allen Simpson wrote:
>> David Miller wrote:
>>> Your patch is broken, please don't wate my time like this.
>>>
>>> + git apply --check --whitespace=error-all diff
>>> error: patch failed: drivers/net/ppp_async.c:36
>>> error: drivers/net/ppp_async.c: patch does not apply
>>>
>> What David may have meant, had he followed Documentation/ManagementStyle
>> or had any project management skills what-so-ever, is that you need to
>> follow Documentation/SubmittingPatches more carefully.
>
> I think this time it was only about a missing tab ;-)
>
> Jarek P.
>
>>
>> Look at 15) The canonical patch format
>>
>> [PATCH 17/11] makes no sense, you don't have 11 patches, and the 17th
>> patch of 11 can never exist.
>>
>> Need a better "subsystem: summary phrase", perhaps
>> "net: PPP buffer too small for higher speed connections"
>>
>> A marker line containing simply "---".
>>
>> And your trailer boilerplate badly breaks the system, because it's
>> missing the SMTP email standard "--" line in front of it.
>>
>> You'll get nicer formatting with 'git format-patch -o ~ HEAD~1' after you
>> do a 'git commit -a' on your git tree.
>>
>> It takes some time, even for a simple 1 line fix like this....
>>
>> Hope that helps.
>> --
>> 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
>>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2009-11-17 11:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 9:19 fangxiaozhi 00110321
2009-11-17 9:22 ` David Miller
2009-11-17 10:20 ` William Allen Simpson
2009-11-17 11:14 ` Jarek Poplawski
2009-11-17 11:49 ` William Allen Simpson
2009-11-17 11:54 ` Franko Fang [this message]
2009-11-17 11:49 ` David Miller
2009-11-18 5:04 ` William Allen Simpson
2009-11-18 7:51 ` Jarek Poplawski
2009-11-21 9:29 ` Pavel Machek
2009-11-21 12:21 ` Jarek Poplawski
2009-11-21 19:00 ` David Miller
2009-11-17 17:37 ` Alexander Clouter
2009-11-17 18:49 ` Valdis.Kletnieks
2009-11-18 4:00 ` William Allen Simpson
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='00b301ca677c$c03f25d0$76900b0a@china.huawei.com' \
--to=huananhu@huawei.com \
--cc=davem@davemloft.net \
--cc=jarkao2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=william.allen.simpson@gmail.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®