All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] param: Adapt MN10300 to the new parameter handling regime
Date: Sun, 7 Dec 2008 19:51:18 +1030	[thread overview]
Message-ID: <200812071951.18907.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200812052325.22974.rusty@rustcorp.com.au>

On Friday 05 December 2008 23:25:22 Rusty Russell wrote:
> On Friday 05 December 2008 22:28:16 David Howells wrote:
> > With that, the core_param stuff does work for mem=...
...
> > It should, perhaps,
> > appear in /proc/cmdline, but for some reason it does not.
> 
> Hmm, that's more concering.  I'll dig into this in the morning.

OK, I can't reproduce it.  I was thinking some weird corner case
with not restoring the string in parse_args, but putting in a dummy
"mem" core_param() on x86 works as first, middle and last arg on cmdline,
and command line shows up correctly in /proc/cmdline.

Any chance I can ask you to verify that?  Is the commandline printk'd
on boot also wrong?

Thanks,
Rusty.

  parent reply	other threads:[~2008-12-07  9:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 16:32 [PATCH 1/3] param: Adapt MN10300 to the new parameter handling regime David Howells
2008-12-03 16:32 ` [PATCH 2/3] [PATCH] param: Stop gcc from inlining empty weak functions David Howells
2008-12-05  8:28   ` Rusty Russell
2008-12-05 12:02     ` David Howells
2008-12-03 16:32 ` [PATCH 3/3] [PATCH] param: Adapt FRV to the new parameter handling regime David Howells
2008-12-05  8:25 ` [PATCH 1/3] param: Adapt MN10300 " Rusty Russell
2008-12-05 11:58   ` David Howells
2008-12-05 12:55     ` Rusty Russell
2008-12-05 13:07       ` David Howells
2008-12-07  9:21       ` Rusty Russell [this message]
2008-12-10 10:39         ` David Howells

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=200812071951.18907.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.