mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alon Bar-Lev" <alon.barlev@gmail.com>
To: "akpm@osdl.org" <akpm@osdl.org>
Cc: mm-commits@vger.kernel.org, davem@davemloft.net,
	"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: + dynamic-kernel-command-line-sparc64-fix.patch added to -mm tree
Date: Sat, 27 Jan 2007 13:14:57 +0200	[thread overview]
Message-ID: <9e0cf0bf0701270314t3369dc7fke7fe8589be1d5bd7@mail.gmail.com> (raw)
In-Reply-To: <200701271103.l0RB32ES007734@shell0.pdx.osdl.net>

On 1/27/07, akpm@osdl.org <akpm@osdl.org> wrote:
> diff -puN drivers/sbus/char/openprom.c~dynamic-kernel-command-line-sparc64-fix drivers/sbus/char/openprom.c
> --- a/drivers/sbus/char/openprom.c~dynamic-kernel-command-line-sparc64-fix
> +++ a/drivers/sbus/char/openprom.c
> @@ -283,7 +283,7 @@ static int oprompath2node(void __user *a
>
>  static int opromgetbootargs(void __user *argp, struct openpromio *op, int bufsize)
>  {
> -       char *buf = saved_command_line;
> +       char *buf = boot_command_line;
>         int len = strlen(buf);
>
>         if (len > bufsize)

Hello Andrew,

I don't think this is correct.
The boot_command_line should only be used by init code.
Drivers should continue to use saved_command_line.

I don't know why saved_command_line cannot be resolved and
boot_command_line can be.
They are both located in linux/init.h

extern char __initdata boot_command_line[];
extern char *saved_command_line;

And the drivers/sbus/char/openprom.c do include it and I assume
__ASSEMBLY__ is not defined.

Best Regards,
Alon Bar-Lev.

       reply	other threads:[~2007-01-27 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200701271103.l0RB32ES007734@shell0.pdx.osdl.net>
2007-01-27 11:14 ` Alon Bar-Lev [this message]
2007-01-27 11:29   ` Andrew Morton

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=9e0cf0bf0701270314t3369dc7fke7fe8589be1d5bd7@mail.gmail.com \
    --to=alon.barlev@gmail.com \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.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

all inboxes | Powered by JetHome®