Re: [PATCH] firmware: Allow release-specific firmware dir

From: Kai Henningsen
Date: Fri Sep 12 2008 - 16:25:16 EST


On Fri, Sep 12, 2008 at 16:32, David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote:
> On Fri, 2008-09-12 at 04:39 -0400, Joseph Fannin wrote:
>> On Thu, Sep 11, 2008 at 03:25:43PM -0700, David Woodhouse wrote:
>> > On Thu, 2008-09-11 at 15:07 -0700, Greg KH wrote:
>> <snip>
>>
>> > Now, can we _please_ stop being bloody stupid? If there are _real_
>> > problems, like the one I fixed with commit 1cede1af last week, then I'm
>> > perfectly happy to deal with them. But stop making crap up.
>>
>> I CAN'T INSTALL MORE THAN ONE KERNEL PACKAGE > v2.6.26.
>>
>> IT'S NOT IMAGINARY.
>>
>> IT USED TO WORK AND YOU BROKE IT.
>
> Then your kernel packaging is broken. Fix it.

I might be confused here, but my impression is that he complains about
packaging that is part of the kernel sources. That really makes it a
stretch to call it "his" packaging.

Let's see ... yes, scripts/packaging stuff ... assuming I parsed
MAINTAINERS correctly, that means it belongs to

KERNEL BUILD (kbuild: Makefile, scripts/Makefile.*)
P: Sam Ravnborg
M: sam@xxxxxxxxxxxx
T: git kernel.org:/pub/scm/linux/kernel/git/sam/kbuild-next.git
T: git kernel.org:/pub/scm/linux/kernel/git/sam/kbuild-fixes.git
L: linux-kbuild@xxxxxxxxxxxxxxx
S: Maintained

No?

I've never used that stuff myself. I prefer working with the (Debian)
kernel-package (make-kpkg) tool, which is also used to create the
distribution packages I believe, and which when I last used it
certainly had an active maintainer.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/