Re: Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length

[Baodong Chen]

On Sun, Jan 4, 2009 at 8:57 PM, Ingo Molnar <mingo@xxxxxxx> wrote:
>
> * Baodong Chen <chenbdchenbd@xxxxxxxxx> wrote:
>
>> On Fri, Jan 2, 2009 at 5:26 PM, Ingo Molnar <mingo@xxxxxxx> wrote:
>> >
>> > * Baodong Chen <chenbdchenbd@xxxxxxxxx> wrote:
>> >
>> >>  Documentation/x86/boot.txt:payload length was changed to payload_length
>> >>
>> >> Signed-off-by: Baodong Chen <[email]chenbdchenbd@xxxxxxxxx[email]>
>> >>
>> >> ---
>> >>  Documentation/x86/boot.txt |    2 +-
>> >>  1 files changed, 1 insertions(+), 1 deletions(-)
>> >
>> > looks good but the patch was whitespace damaged (all tabs were spaces and
>> > there were linewraps as well), please check
>> > Documentation/email-clients.txt and resend the patch. Thanks,
>> >
>> >        Ingo
>>
>> I referred to Documentation/email-clients.txt:Gmail and resent the
>> patch. I am a newbie,if i made any mistake,please do me a favor and help
>> me.Thanks!
>
> it's OK, and your resubmission was better - but it still had a linewrap
> problem (i was able to fix that up manually).
>
> this bit:
>
> @@ -44,7 +44,7 @@ Protocol 2.07:        (Kernel 2.6.24) Added paravirtualised
> boot protocol.
>                and KEEP_SEGMENTS flag in load_flags.
>
> [3 lines]
>
> should have been:
>
> @@ -44,7 +44,7 @@ Protocol 2.07:        (Kernel 2.6.24) Added paravirtualised boot protocol.
>                and KEEP_SEGMENTS flag in load_flags.
>
> [2 lines]
>
> If you post from gmail it might make sense to send patches as MIME
> attachments, we can process them just fine. (as long as you send patches
> that go via -tip - other maintainers have different policies regarding
> MIME attachments)
>
>        Ingo
>
I am sorry for my linewrap problem.i used Gmail GUI with gedit to write
the mailbody.you meat that if i send path via -tip, i can send my patch
content as attachment file?got it...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/