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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.0901041453170.26359@swampdragon.chaosbits.net>
Date:	Sun, 4 Jan 2009 14:55:31 +0100 (CET)
From:	Jesper Juhl <jj@...osbits.net>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Baodong Chen <chenbdchenbd@...il.com>,
	linux-kernel@...r.kernel.org, trivial@...nel.org,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: Subject: [PATCH] Documentation/x86/boot.txt:payload length was
 changed to payload_length

On Sun, 4 Jan 2009, Ingo Molnar wrote:

> 
> * Baodong Chen <chenbdchenbd@...il.com> wrote:
> 
> > On Fri, Jan 2, 2009 at 5:26 PM, Ingo Molnar <mingo@...e.hu> wrote:
> > >
> > > * Baodong Chen <chenbdchenbd@...il.com> wrote:
> > >
> > >>  Documentation/x86/boot.txt:payload length was changed to payload_length
> > >>
> > >> Signed-off-by: Baodong Chen <[email]chenbdchenbd@...il.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@...osbits.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/