LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Shaohua Li <shaohua.li@intel.com>,
	Daniel J Blueman <daniel.blueman@gmail.com>,
	jamagallon@ono.com, tigran@aivazian.fsnet.co.uk,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: New format Intel microcode...
Date: Mon, 26 Mar 2007 01:52:48 -0700	[thread overview]
Message-ID: <460789E0.1000600@linux.intel.com> (raw)
In-Reply-To: <1174898060.5815.11.camel@violet>

Marcel Holtmann wrote:
> that is the whole point. The slash was never meant to be used. It was
> designed to take a filename or a pattern that will be later matched by
> userspace. However some developers are now trying to abuse this since
> the simple firmware helper script matches this directly to a filename
> (and directory in this case) on the disk.
> 
> Putting a slash in the request_firmware() call now enforces a
> subdirectory 

I don't see how this follows from the former. Userspace is free to 
translate the kernel string into anything it wants, even a simple 
replacement of / with _. So I don't see how this "enforces" a 
subdirectory. Firmware gets a namespace basically, and a / is a 
logical namespace separator.

  reply	other threads:[~2007-03-26  8:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 23:45 Daniel J Blueman
2007-03-23  0:43 ` Shaohua Li
2007-03-23  9:43   ` Marcel Holtmann
2007-03-23  9:03     ` Arjan van de Ven
2007-03-26  8:34       ` Marcel Holtmann
2007-03-26  8:52         ` Arjan van de Ven [this message]
2007-06-26 21:42   ` Daniel J Blueman
2007-06-26 23:29     ` Andi Kleen
2007-06-28 13:53       ` Bill Davidsen
2007-06-28 14:12         ` Arjan van de Ven
2007-06-28 15:48           ` Alex Riesen
2007-06-28 17:27           ` Chuck Ebbert
2007-06-28 17:29             ` Arjan van de Ven
2007-06-28 17:54             ` Daniel J Blueman
2007-06-28 15:27         ` Andi Kleen
2007-06-28 15:44           ` Chuck Ebbert
2007-06-28 22:55             ` Bill Davidsen
2007-06-28 22:23           ` Bill Davidsen
2007-06-28 22:30             ` Arjan van de Ven
2007-06-28 23:09             ` Andi Kleen
2007-07-02  8:56   ` Alex Riesen
2007-07-02 17:18     ` Arjan van de Ven
2007-07-02 18:22       ` Alex Riesen

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=460789E0.1000600@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=daniel.blueman@gmail.com \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=shaohua.li@intel.com \
    --cc=tigran@aivazian.fsnet.co.uk \
    --subject='Re: New format Intel microcode...' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).