From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Andrey Borzenkov <arvidjaar-JGs/UdohzUI@public.gmane.org>
Cc: "initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] udev: install distro specific firmware handler
Date: Fri, 26 Feb 2010 16:41:22 +0100 [thread overview]
Message-ID: <4B87EBA2.20206@bfh.ch> (raw)
In-Reply-To: <201002261818.37491.arvidjaar-JGs/UdohzUI@public.gmane.org>
Andrey Borzenkov wrote:
> On Friday 26 of February 2010 17:39:29 Philippe Seewer wrote:
>> Debian Unstable still calls its firmware handling script
>> 'firmware.agent' instead of 'firmware.sh'. This patch ensures that
>> either the .agent or the .sh gets installed.
>> ---
>> modules.d/95udev-rules/install | 5 +++--
>> 1 files changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/modules.d/95udev-rules/install
>> b/modules.d/95udev-rules/install index b903a41..287cc03 100755
>> --- a/modules.d/95udev-rules/install
>> +++ b/modules.d/95udev-rules/install
>> @@ -15,7 +15,9 @@ inst_rules "$moddir/01-ignore.rules"
>>
>> # for firmware loading
>> inst_rules 50-firmware.rules
>> -dracut_install /lib/udev/firmware.sh
>
> Your patch seems to be against old codebase. This has changed in current
> GIT (and 004 actually) already to account for binary /lib/udev/firmware
> shipped with new udev.
Now I'm confused... according to git's history there's only been two
changes to 95udev-rules/install in the last 4-5 months.
next prev parent reply other threads:[~2010-02-26 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 14:39 [PATCH] udev: install distro specific firmware handler Philippe Seewer
[not found] ` <1267195175-15554-1-git-send-email-philippe.seewer-omB+W0Dpw2o@public.gmane.org>
2010-02-26 15:18 ` Andrey Borzenkov
[not found] ` <201002261818.37491.arvidjaar-JGs/UdohzUI@public.gmane.org>
2010-02-26 15:41 ` Seewer Philippe [this message]
[not found] ` <4B87EBA2.20206-omB+W0Dpw2o@public.gmane.org>
2010-02-26 16:35 ` Andrey Borzenkov
2010-03-04 13:08 ` Harald Hoyer
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=4B87EBA2.20206@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=arvidjaar-JGs/UdohzUI@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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