All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
	linux-kernel@vger.kernel.org, jaswinder@infradead.org
Subject: Re: [PATCH] ip2: use request_firmware()
Date: Mon, 16 Jun 2008 16:21:53 -0400	[thread overview]
Message-ID: <4856CB61.6030202@garzik.org> (raw)
In-Reply-To: <20080616205820.1fe298d7@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> There is no reason why firmware must be artificially separated into 
>> firmware/
> 
> It seems a good step towards kicking it all out of the kernel tree into
> user space where it belongs.

Why does that goal need a toplevel directory in the kernel source tree, 
one that ultimately must mirror the other hierarchies already in the tree?

It's better to have drivers/char/ip2.ihex and keep everything related to 
a single driver in one place.

Extracting the firmware:  good

Scattering a /single/ driver across multiple directories in the kernel 
tree:  bad

	Jeff




  reply	other threads:[~2008-06-16 20:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16  9:49 [PATCH] ip2: use request_firmware() David Woodhouse
2008-06-16 10:59 ` Alan Cox
2008-06-16 12:06   ` David Woodhouse
2008-06-16 20:02   ` Jeff Garzik
2008-06-16 19:56     ` Alan Cox
2008-06-16 20:05     ` Jeff Garzik
2008-06-16 19:58       ` Alan Cox
2008-06-16 20:21         ` Jeff Garzik [this message]
2008-06-16 20:21           ` Alan Cox
2008-06-16 21:39             ` Jeff Garzik
2008-06-16 21:34               ` Alan Cox
2008-06-16 22:01               ` David Woodhouse
2008-06-16 20:12 ` Jeff Garzik
2008-06-16 20:00   ` Alan Cox
2008-06-16 20:22     ` Jeff Garzik
2008-06-16 20:21       ` Alan Cox

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=4856CB61.6030202@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=jaswinder@infradead.org \
    --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.