linux-kernel - Re: [PULL] Miscellaneous trivialities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 16 Aug 2013 10:48:16 -0500
From:	Rob Landley <rob@...dley.net>
To:	Michael Witten <mfwitten@...il.com>
Cc:	Jiri Kosina <trivial@...nel.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org
Subject: Re: [PULL] Miscellaneous trivialities

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:
> 
>   [1] Docs: Kconfig: For readability, offset modifiers with commas
>   [2] Docs: Kconfig: Use consistent whitespace indentation
>   [3] Docs: Kconfig: Clean up the radiotap documentation
>   [4] Docs: Kconfig: `devlopers' -> `developers'
>   [5] Docs: Replace `hotplug' with `udev'
>   [6] DRM: comment: halve -> half
>   [7] DRM: comment: gdm_proc_lists -> drm_proc_lists
>   [8] DRM: cleanup: Remove unused `gamma_size'
> 
>   Documentation/networking/README.ipw2200 |   5 +-
>   drivers/gpu/drm/drm_fb_helper.c         |   3 -
>   drivers/gpu/drm/drm_irq.c               |   4 +-
>   drivers/gpu/drm/drm_proc.c              |   2 +-
>   drivers/net/wireless/ipw2x00/Kconfig    | 102  
> ++++++++++++++++----------------
>   fs/btrfs/Kconfig                        |   3 +-
>   init/Kconfig                            |   4 +-
>   7 files changed, 60 insertions(+), 63 deletions(-)
> 
> Those commits merge cleanly with:
> 
>   28fbc8b6a29c849a3f03a6b05010d4b584055665
>   Merge branch 'sched-urgent-for-linus' of
>     git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
>     (2013-08-13 16:58:17 -0700)
> 
> and they can be pulled from here:
> 
>   https://github.com/mfwitten/linux.git trivial/misc/0
> 
> While it is much easier to review the individual commits, a combined
> diff is appended to the end of this email in case that is convenient.
> 
> Sincerely
> Michael Witten
> 
> ----------------------------------------------------------------
> 
> 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.

Rob--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/