From: Daniel Walker <dwalker@fifo99.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>,
uclinux-dev@uclinux.org
Subject: Re: [PATCH] Add uboot commandline argument passing support to m68knommu
Date: Fri, 18 Sep 2009 09:39:04 -0700 [thread overview]
Message-ID: <1253291944.7060.42.camel@desktop> (raw)
In-Reply-To: <20090918162736.GY23700@csclub.uwaterloo.ca>
On Fri, 2009-09-18 at 12:27 -0400, Lennart Sorensen wrote:
> +
> + if (uboot_cmd_start && uboot_cmd_end) {
> + strncpy(commandp, (const char *)uboot_cmd_start,
> size);
> + }
> +#if defined(CONFIG_BLK_DEV_INITRD)
> + if (uboot_initrd_start && uboot_initrd_end &&
> + (uboot_initrd_end > uboot_initrd_start))
> {
> + initrd_start = uboot_initrd_start;
> + initrd_end = uboot_initrd_end;
> + ROOT_DEV = Root_RAM0;
> + printk("initrd at 0x%lx:0x%lx\n",
> + initrd_start, initrd_end);
> + }
> +#endif /* if defined(CONFIG_BLK_DEV_INITRD) */
> +}
You have a couple of various checkpatch errors in this patch. We use
scripts/checkpatch.pl to check for code style issues. Could you run that
on your patch and fix any errors it finds? A couple are whitespace
related and you can use scripts/cleanpatch or scripts/cleanfile to
remove whitespace (so I hear. I've never run those scripts personally)
Daniel
next prev parent reply other threads:[~2009-09-18 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 16:27 [PATCH] Add uboot commandline argument passing support to m68knommu Lennart Sorensen
2009-09-18 16:39 ` Daniel Walker [this message]
2009-09-18 17:49 ` [PATCH] Add uboot commandline argument passing support to m68knommu (Try #2) Lennart Sorensen
2009-09-18 17:54 ` Daniel Walker
2009-10-01 6:28 ` [uClinux-dev] " Greg Ungerer
2009-10-02 14:32 ` Lennart Sorensen
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=1253291944.7060.42.camel@desktop \
--to=dwalker@fifo99.com \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=uclinux-dev@uclinux.org \
/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