* Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length @ 2009-01-02 8:24 Baodong Chen 2009-01-02 9:26 ` Ingo Molnar 0 siblings, 1 reply; 6+ messages in thread From: Baodong Chen @ 2009-01-02 8:24 UTC (permalink / raw) To: linux-kernel; +Cc: trivial Documentation/x86/boot.txt:payload length was changed to payload_length Signed-off-by: Baodong Chen <[email]chenbdchenbd@gmail.com[email]> --- Documentation/x86/boot.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Documentation/x86/boot.txt b/Documentation/x86/boot.txt index fcdc62b..7b4596a 100644 --- a/Documentation/x86/boot.txt +++ b/Documentation/x86/boot.txt @@ -44,7 +44,7 @@ Protocol 2.07: (Kernel 2.6.24) Added paravirtualised boot protocol. and KEEP_SEGMENTS flag in load_flags. Protocol 2.08: (Kernel 2.6.26) Added crc32 checksum and ELF format - payload. Introduced payload_offset and payload length + payload. Introduced payload_offset and payload_length fields to aid in locating the payload. Protocol 2.09: (Kernel 2.6.26) Added a field of 64-bit physical -- 1.5.3.3 ^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length 2009-01-02 8:24 Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length Baodong Chen @ 2009-01-02 9:26 ` Ingo Molnar 2009-01-03 4:44 ` Baodong Chen 0 siblings, 1 reply; 6+ messages in thread From: Ingo Molnar @ 2009-01-02 9:26 UTC (permalink / raw) To: Baodong Chen; +Cc: linux-kernel, trivial, H. Peter Anvin * Baodong Chen <chenbdchenbd@gmail.com> wrote: > Documentation/x86/boot.txt:payload length was changed to payload_length > > Signed-off-by: Baodong Chen <[email]chenbdchenbd@gmail.com[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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length 2009-01-02 9:26 ` Ingo Molnar @ 2009-01-03 4:44 ` Baodong Chen 2009-01-04 12:57 ` Ingo Molnar 0 siblings, 1 reply; 6+ messages in thread From: Baodong Chen @ 2009-01-03 4:44 UTC (permalink / raw) To: Ingo Molnar; +Cc: linux-kernel, trivial, H. Peter Anvin On Fri, Jan 2, 2009 at 5:26 PM, Ingo Molnar <mingo@elte.hu> wrote: > > * Baodong Chen <chenbdchenbd@gmail.com> wrote: > >> Documentation/x86/boot.txt:payload length was changed to payload_length >> >> Signed-off-by: Baodong Chen <[email]chenbdchenbd@gmail.com[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! ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length 2009-01-03 4:44 ` Baodong Chen @ 2009-01-04 12:57 ` Ingo Molnar 2009-01-04 13:49 ` Baodong Chen 2009-01-04 13:55 ` Jesper Juhl 0 siblings, 2 replies; 6+ messages in thread From: Ingo Molnar @ 2009-01-04 12:57 UTC (permalink / raw) To: Baodong Chen; +Cc: linux-kernel, trivial, H. Peter Anvin * Baodong Chen <chenbdchenbd@gmail.com> wrote: > On Fri, Jan 2, 2009 at 5:26 PM, Ingo Molnar <mingo@elte.hu> wrote: > > > > * Baodong Chen <chenbdchenbd@gmail.com> wrote: > > > >> Documentation/x86/boot.txt:payload length was changed to payload_length > >> > >> Signed-off-by: Baodong Chen <[email]chenbdchenbd@gmail.com[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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length 2009-01-04 12:57 ` Ingo Molnar @ 2009-01-04 13:49 ` Baodong Chen 2009-01-04 13:55 ` Jesper Juhl 1 sibling, 0 replies; 6+ messages in thread From: Baodong Chen @ 2009-01-04 13:49 UTC (permalink / raw) To: Ingo Molnar; +Cc: linux-kernel, trivial, H. Peter Anvin On Sun, Jan 4, 2009 at 8:57 PM, Ingo Molnar <mingo@elte.hu> wrote: > > * Baodong Chen <chenbdchenbd@gmail.com> wrote: > >> On Fri, Jan 2, 2009 at 5:26 PM, Ingo Molnar <mingo@elte.hu> wrote: >> > >> > * Baodong Chen <chenbdchenbd@gmail.com> wrote: >> > >> >> Documentation/x86/boot.txt:payload length was changed to payload_length >> >> >> >> Signed-off-by: Baodong Chen <[email]chenbdchenbd@gmail.com[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... ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length 2009-01-04 12:57 ` Ingo Molnar 2009-01-04 13:49 ` Baodong Chen @ 2009-01-04 13:55 ` Jesper Juhl 1 sibling, 0 replies; 6+ messages in thread From: Jesper Juhl @ 2009-01-04 13:55 UTC (permalink / raw) To: Ingo Molnar; +Cc: Baodong Chen, linux-kernel, trivial, H. Peter Anvin On Sun, 4 Jan 2009, Ingo Molnar wrote: > > * Baodong Chen <chenbdchenbd@gmail.com> wrote: > > > On Fri, Jan 2, 2009 at 5:26 PM, Ingo Molnar <mingo@elte.hu> wrote: > > > > > > * Baodong Chen <chenbdchenbd@gmail.com> wrote: > > > > > >> Documentation/x86/boot.txt:payload length was changed to payload_length > > >> > > >> Signed-off-by: Baodong Chen <[email]chenbdchenbd@gmail.com[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) > Or simply don't use Gmails web interface for sending the emails. I used to use Gmail in the past, but I used it with Pine or Alpine most of the time. Alpine can be configured to send proper emails and just use Gmails SMTP server for sending them - Mutt also works fine. -- Jesper Juhl <jj@chaosbits.net> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-01-04 13:55 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-01-02 8:24 Subject: [PATCH] Documentation/x86/boot.txt:payload length was changed to payload_length Baodong Chen 2009-01-02 9:26 ` Ingo Molnar 2009-01-03 4:44 ` Baodong Chen 2009-01-04 12:57 ` Ingo Molnar 2009-01-04 13:49 ` Baodong Chen 2009-01-04 13:55 ` Jesper Juhl
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox