From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] Cleanup the comment for m68k linux boot argument passing.
Date: Fri, 20 Feb 2009 12:41:31 -0500 [thread overview]
Message-ID: <200902201241.32006.vapier@gentoo.org> (raw)
In-Reply-To: <499EE6E6.1030507@RuggedCom.com>
On Friday 20 February 2009 12:22:46 Richard Retanubun wrote:
> From d1e6b372d1781f15f1042fa379562f85c873405a Mon Sep 17 00:00:00 2001
> From: Richard Retanubun <RichardRetanubun@RuggedCom.com>
> Date: Fri, 20 Feb 2009 11:06:36 -0500
> Subject: [PATCH] Cleanup the comment for m68k linux boot argument passing.
> The one gotcha here is that the assembly instruction that
> the compiler uses to jump to the kernel is 'jsr' which pushes the
> program counter for the instruction after the jsr into the stack pointer.
there has to be a new line between the summary and the explanatory paragraph,
otherwise the entire text is used as the subject ... as for the actual
content, i have no comment as i dont know m68k at all ;)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090220/f9fe7326/attachment.pgp
next prev parent reply other threads:[~2009-02-20 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 16:57 [U-Boot] Coldfire: bootm: How does bootm pass bootargs to linux? Richard Retanubun
2009-02-19 0:07 ` TC Liew
2009-02-20 16:34 ` [U-Boot] [PATCH] Cleanup the comment for m68k linux boot argument passing Richard Retanubun
2009-02-20 17:02 ` Mike Frysinger
2009-02-20 17:15 ` Richard Retanubun
2009-02-20 17:22 ` [U-Boot] [PATCH V2] " Richard Retanubun
2009-02-20 17:41 ` Mike Frysinger [this message]
2009-02-20 18:01 ` Richard Retanubun
2009-02-21 22:50 ` Wolfgang Denk
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=200902201241.32006.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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