From: Rusty Russell <rusty@rustcorp.com.au>
To: Len Brown <len.brown@intel.com>
Cc: Werner Almesberger <werner@almesberger.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] boot parameters: quoting of environmentvariablesrevisited
Date: Wed, 20 Oct 2004 18:03:10 +1000 [thread overview]
Message-ID: <1098259389.10571.149.camel@localhost.localdomain> (raw)
In-Reply-To: <1098258821.26595.4324.camel@d845pe>
On Wed, 2004-10-20 at 17:53, Len Brown wrote:
> On Wed, 2004-10-20 at 03:35, Rusty Russell wrote:
> > On Wed, 2004-10-20 at 17:16, Len Brown wrote:
> > > I verified that this new patch doesn't break the
> > acpi_os_string="Brand X" kernel parameter.
> >
> > I can't find where acpi_os_string is handled: grepping the latest
> > kernel gives nothing, but I'd expect the quotes to be stripped.
>
> s/acpi_os_string/acpi_os_name
Ah, looks like that code strips the " anyway, so the fact that we're now
doing it just means it can be simplified.
Cheers!
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-10-20 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 22:23 [PATCH] boot parameters: quoting of environment variables revisited Werner Almesberger
2004-10-20 1:04 ` Andrew Morton
2004-10-20 1:47 ` Werner Almesberger
2004-10-20 6:21 ` Rusty Russell
2004-10-20 7:16 ` [PATCH] boot parameters: quoting of environment variablesrevisited Len Brown
2004-10-20 7:35 ` Rusty Russell
2004-10-20 7:53 ` [PATCH] boot parameters: quoting of environmentvariablesrevisited Len Brown
2004-10-20 8:03 ` Rusty Russell [this message]
2004-10-22 1:01 ` Rusty Russell
2004-10-20 9:04 ` [PATCH] boot parameters: quoting of environment variablesrevisited Werner Almesberger
2004-10-20 9:27 ` [PATCH] boot parameters: quoting of environment variables revisited Werner Almesberger
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=1098259389.10571.149.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=werner@almesberger.net \
/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.