From: Michael Witten <mfwitten@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: Jiri Kosina <trivial@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org
Subject: Re: [PULL] Miscellaneous trivialities
Date: Fri, 16 Aug 2013 20:02:23 -0000 [thread overview]
Message-ID: <44b5fd3b87ba4565a78f1da4fa7d2e7d-mfwitten@gmail.com> (raw)
In-Reply-To: <1376668096.2737.43@driftwood>
On Fri, 16 Aug 2013 10:48:16 -0500, Rob Landley wrote:
> On 08/15/2013 04:44:01 AM, Michael Witten wrote:
>
>> I've been sitting on some trivial patches for a while, and I'd just
>> like to get them out of the way.
>>
>> Here is the series:
>>
>> ...
>>
>> [5] Docs: Replace `hotplug' with `udev'
>>
>> ...
>>
>> diff --git a/Documentation/networking/README.ipw2200 b/Documentation/networking/README.ipw2200
>> index b7658be..aeb6494 100644
>> --- a/Documentation/networking/README.ipw2200
>> +++ b/Documentation/networking/README.ipw2200
>> @@ -256,7 +256,7 @@ You can set the debug level via:
>>
>> Where $VALUE would be a number in the case of this sysfs entry. The
>> input to sysfs files does not have to be a number. For example, the
>> -firmware loader used by hotplug utilizes sysfs entries for transferring
>> +firmware loader used by udev utilizes sysfs entries for transferring
>> the firmware image from user space into the driver.
>
> Hotplug is the name of the kernel subsystem, udev was one implementation
> of a userspace agent for it. A different implementation would be mdev
> (in busybox), some linux from scratch types are still using variants of
> diethotplug, there's a fork of udev called eudev that avoids systemd...
>
> And these days, firmware loading is mostly done directly by the kernel.
>
>> The Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries
>> @@ -425,8 +425,7 @@ are made to the driver. Currently, there are no major changes planned.
>> ----------------------------------------------
>>
>> The driver requires a firmware image, download it and extract the
>> -files under /lib/firmware (or wherever your hotplug's firmware.agent
>> -will look for firmware files)
>> +files under /lib/firmware (or wherever udev will look for firmware files)
>
> Again, hotplug is correct.
Thanks for catching my error. I removed that patch from the series; the
remaining commits can be pulled from here:
https://github.com/mfwitten/linux.git trivial/misc/1
next prev parent reply other threads:[~2013-08-17 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 9:44 Michael Witten
2013-08-15 16:23 ` Randy Dunlap
2013-08-16 15:48 ` Rob Landley
2013-08-16 20:02 ` Michael Witten [this message]
[not found] ` <f0d1a6bf084b4f45a32b9d156788041f-mfwitten@gmail.com>
2013-08-20 10:50 ` Jiri Kosina
2013-08-20 14:24 ` Michael Witten
2013-08-20 16:23 ` Michael Witten
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=44b5fd3b87ba4565a78f1da4fa7d2e7d-mfwitten@gmail.com \
--to=mfwitten@gmail.com \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rob@landley.net \
--cc=trivial@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
Powered by JetHome