All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <asharma@fb.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Michal Marek <mmarek@suse.cz>, Arun Sharma <asharma@fb.com>,
	linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add $KERNELRELEASE to firmware install path
Date: Fri, 6 May 2011 11:44:38 -0700	[thread overview]
Message-ID: <20110506184438.GA30417@dev1756.snc6.facebook.com> (raw)
In-Reply-To: <1304677113.20656.2.camel@i7.infradead.org>

On Fri, May 06, 2011 at 11:18:32AM +0100, David Woodhouse wrote:
> On Fri, 2011-05-06 at 12:15 +0200, Michal Marek wrote:
> > 
> > On 5.5.2011 19:39, Arun Sharma wrote:
> > > Useful in the presence of multiple kernels with different
> > > firmware versions.
> > 
> > The changelog should also include the udev version that is able to find 
> > the firmware there (v127, August 2008). FWIW, SUSE has been using this 
> > patch since about that time, but we forgot to push this :-|. Anyway
> 
> No, this is fundamentally broken. Do not do it.
> 
> The firmware lives in /lib/firmware, not in /lib/firmware/$KERNELVERSION

I'm not trying to change the way the kernel deals with firmware or
anything. Just trying to make the vanilla kernel packaging scripts more
usable for us.

Without this change, if you have two kernel rpms/debs from different
kernel versions installed, they'll result in a namespace conflict
(rpm/deb install will fail), which gets resolved by this patch.

  -Arun

  reply	other threads:[~2011-05-06 18:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 17:39 [PATCH] Add $KERNELRELEASE to firmware install path Arun Sharma
2011-05-06 10:15 ` Michal Marek
2011-05-06 10:18   ` David Woodhouse
2011-05-06 18:44     ` Arun Sharma [this message]
2011-05-06 19:02       ` David Woodhouse
2011-05-06 22:37         ` Arun Sharma
2011-05-16 14:21           ` Michal Marek
2011-05-17 11:23             ` David Woodhouse
2011-05-17 11:37               ` Michal Marek

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=20110506184438.GA30417@dev1756.snc6.facebook.com \
    --to=asharma@fb.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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.