public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Arun Sharma <asharma@fb.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add $KERNELRELEASE to firmware install path
Date: Mon, 16 May 2011 16:21:18 +0200	[thread overview]
Message-ID: <20110516142118.GM13293@sepie.suse.cz> (raw)
In-Reply-To: <20110506223727.GA29011@dev1756.snc6.facebook.com>

On Fri, May 06, 2011 at 03:37:27PM -0700, Arun Sharma wrote:
> On Fri, May 06, 2011 at 08:02:36PM +0100, David Woodhouse wrote:
> > On Fri, 2011-05-06 at 11:44 -0700, Arun Sharma wrote:
> > > 
> > > 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. 
> > 
> > The packages are broken then. They shouldn't include *any* files
> > in /lib/firmware.
> > 
> > Fix *that*, and the problem goes away.
> 
> Sounds good.
> 
> Michal: Should I send you a patch that drops /lib/firmware?

make deb-pkg generates a separate package with the firmware files. I
would suggest we do the same for rpm.

Michal

  reply	other threads:[~2011-05-16 14:21 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
2011-05-06 19:02       ` David Woodhouse
2011-05-06 22:37         ` Arun Sharma
2011-05-16 14:21           ` Michal Marek [this message]
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=20110516142118.GM13293@sepie.suse.cz \
    --to=mmarek@suse.cz \
    --cc=asharma@fb.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kbuild@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox