summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/udev/udev-extraconf
Commit message (Collapse)AuthorAgeFilesLines
* udev-extraconf: fix unmount directories containing octal-escaped charsJonathan GUILLOT2024-01-261-1/+1
| | | | | | | | | | | | | | USB devices are auto-mounted in a directory named like theirs labels. Special characters like whitespace are octal-escaped in /proc/mounts output. Using directly this output file as an argument for umount failed and the mount directory can't be removed as still busy. Using printf allows these special characters to be unescaped. (From OE-Core rev: 37f17625d931a06888388682dc2b1f5a2d298125) Signed-off-by: Jonathan GUILLOT <jonathan@joggee.fr> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: mount.sh: check if filesystem is supported before mountingLukas Funke2023-11-101-0/+15
| | | | | | | | | | | | | Check if the filesystem is supported by the kernel before trying to mount it. Systemd-mount will mount the directories asynchronously resulting in stale directories if the devices filesystem is not supported. (From OE-Core rev: 695e0a41e3c1cb47484605934a57e7df591bd19f) Signed-off-by: Lukas Funke <lukas.funke@weidmueller.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf:mount.sh: fix a umount issueMing Liu2022-07-231-1/+1
| | | | | | | | | | | Only touching /tmp/.automount-$name is not good enough, it must contain the mount name, otherwise umount could not get the path from it. (From OE-Core rev: ccea69032329f3ba43c727d9eb71b1d063b89824) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf:mount.sh: fix path mismatching issuesMing Liu2022-07-151-4/+4
| | | | | | | | | | | | | | | | | | | | Since commit f077befd5f36ad88623aaf6a38b1a837ecb18650: [ udev-extraconf: let automount base directory configurable ] the mount base directory was configurable, we need drop 'run-media' usage as well, change to figure it out from MOUNT_BASE. Also 'get_label_name' function needs to be called ealier in automount_systemd before checking '/tmp/.automount-$name', otherwise they would never match. (From OE-Core rev: c013b33162546fb5bd4bcc1daac75aa65d0be1a3) (From OE-Core rev: 7ed210054b3e253d5a67075bb9d4768d1661bef1) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: fix some systemd automount issuesMing Liu2022-06-271-3/+0
| | | | | | | | | | | | | | The '.include' syntax has been dropped from latest systemd releases, we need drop the systemd-udevd.service here, introduce a postinst function to add "MountFlags=shared" to systemd-udevd.service. Also lsblk binary is being called in mount.sh automount_systemd function, add it to RDEPENDS. (From OE-Core rev: 356520d60b9429c6f62124821e42468ff2b7b1d6) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf/mount.sh: ignore lvm in automountMuhammad Hamza2022-06-211-0/+4
| | | | | | | | | | | | | | Failure message is shown in boot logs when trying to mount lvm as automounter does not handle cases where lvm is mounted. This simply skips lvm while automounting to avoid failure message in boot logs. (From OE-Core rev: b1d18072ed9a8b0bca0f20f8e5deefa73ab6acbe) Signed-off-by: Ansar Rasool <ansar_rasool@mentor.com> Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: force systemd-udevd to use shared MountFlagsMuhammad Hamza2022-06-211-0/+3
| | | | | | | | | | | | | | | | | | | Automounting does not work cleanly in case systemd as well as udev rules are being used simultaneously and in most cases race conditions and unknown behavior can come up. In case we're running on top of systemd we need to make sure that systemd-udevd knows that udev is in play as well and mounting should be done using shared flags. Also as we're using mount from sources other than systemd-mount in current scripts this is the most manageable fix to automounting problems. (From OE-Core rev: 1e770416b4c9a0468404fb64d55114d93e84763b) Signed-off-by: Awais Belal <awais_belal@mentor.com> Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf/mount.sh: only mount devices on hotplugMuhammad Hamza2022-06-211-7/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | fdisk from util-linux (2.31.1) and above allows the user to manipulate an already mounted device. In order to achieve this functionality it issues a BLKRRPART (block device re-read part) ioctl and in response the kernel generates remove/change/add events if the device is not mounted (manually unmounted etc) which are caught and processed by udev. This causes our auto-mounter to remount everything because it does not keep track and things go out of control. Differentiating between types of remove events such as the one described above (generated by BLKRRPART) and one where the device is physically plugged out is only possible using the DEVPATH variable which is cleaned up only when the device is actually plugged-out. This fixes the above anomaly by only mounting a device in add event which is cleaned up properly (tmp cache deleted) in the remove event or is not present in the tmp cache while making use of the DEVPATH variable during the remove action. (From OE-Core rev: 11a5e6c17535438ea1e7a8403ed260c8b3a22bc8) Signed-off-by: Awais Belal <awais_belal@mentor.com> Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf/mount.sh: save mount name in our tmp filecacheMuhammad Hamza2022-06-211-1/+4
| | | | | | | | | | | | | | Doing this will allow to fetch the exact name created by the auto-mounter during the remove action where depending on the scenario utilities such as the blkid might not be usable due to actual device not being present on the system. (From OE-Core rev: 496b76f8775a620c1d449eb6f62a41656abf2a9b) Signed-off-by: Awais Belal <awais_belal@mentor.com> Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf/mount.sh: add LABELs to mountpointsMuhammad Hamza2022-06-211-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | This alters the mountpoints such that if a device has a LABEL or a PARTLABEL, it will be mounted at e.g.: /run/media/$LABEL-<device-node> /run/media/$PARTLABEL-<device-node> /run/media/rootfs-sda2 otherwise the device will be mounted at e.g.: /run/media/<device-node> /run/media/sda1 The <device-node> appended with LABEL or PARTLABEL makes sure that the mountpoint is unique, therefore, avoids overlapping mounts. (From OE-Core rev: a9a0a0967832445f1bcc65d58f95343d1b562e1b) Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com> Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: let automount base directory configurableMing Liu2022-06-071-12/+13
| | | | | | | | | | | | Dont hard-code automount base directory to '/run/media', introduce a variable MOUNT_BASE to let it configurable, like in udisks2 the mount base is also configurable by setting option: --enable-fhs-media. (From OE-Core rev: f077befd5f36ad88623aaf6a38b1a837ecb18650) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf/initrdscripts/parted: Rename mount.blacklist -> mount.ignorelistRichard Purdie2022-05-202-2/+2
| | | | | | | | (From OE-Core rev: 69e486ddb3059f80ba538e1f59c2ca8a8df0faf9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: skip mounting partitions already mounted by systemdHector Palacios2019-09-191-0/+6
| | | | | | | | | | | | | | | | | For some devices, udev may sometimes trigger twice the 'add' rule during boot. Calling the mount.sh script twice will eventually fail for already mounted partitions, but in that case, the script tries to remove the created mountpoint, when it shouldn't. This has been observed on USB sticks connected to a USB hub and may result in devices not being mounted if plugged-in before booting. This patch checks for already mounted partitions earlier (before creating the mount point) and returns with no actions. (From OE-Core rev: 4cf076879ac038ebf76679a19249ea6363e63e0f) Signed-off-by: Hector Palacios <hector.palacios@digi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: do not mount swap partitionsOleksandr Kravchuk2019-07-231-0/+4
| | | | | | | | | | | | | | Swap is a special filesystem that cannot be mounted, so do not try to, otherwise we will have service that tries and fails to mount it with the following error: systemd[1]: Mounting /run/media/nvme0n1p3... mount[1229]: mount: /run/media/nvme0n1p3: unknown filesystem type 'swap'. (From OE-Core rev: 7a2c56da85326043f0663c29535ac3fb555d96fe) Signed-off-by: Oleksandr Kravchuk <oleksandr.kravchuk@pelagicore.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Skip the entry in /etc/fstab when using the systemd-mountKevin Hao2018-10-251-0/+9
| | | | | | | | | | | When using systemd, the systemd-fstab-generator would parse the /etc/fstab and create the corresponding unit dynamically. So we don't need to handle the ADD action for the partitions in /etc/fstab. (From OE-Core rev: 6104109ceba1a1323e42d67a632921fb91184ab6) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Fix the recursively dependency for the systemd-mountKevin Hao2018-10-251-11/+14
| | | | | | | | | | | | | | | | The commit 4ca9402c3720 ("udev-extraconf: Add systemd-mount to udev-extraconf/mount.sh") uses the systemd-mount to mount the new added disk partitions if systemd is used. But it forgot to move the codes which tries to mount the partition by using the configuration in /etc/fstab to the non-systemd function. And it will cause the systemd-mount try to mount the partition synchronously and trigger a recursively dependency like the following: dev-sda1.device -> run-media-sda1.mount -> dev-sda1.device (From OE-Core rev: fcf6a4d629c05048cbb7298e285d84ff73a320d2) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Use the canonical file name of systemdKevin Hao2018-10-251-1/+1
| | | | | | | | | | | | | | | The new version of systemd has changed the symbolic link between /sbin/init and /lib/systemd/systemd to relative. So the output of the command 'readlink /sbin/init' become: ../lib/systemd/systemd Then it causes the following check of "/lib/systemd/systemd" to return false. Fix this issue by using the canonical file name of the systemd. (From OE-Core rev: 352b3f0b07370d8df7d6ae13c0bac0697f7751ba) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Add systemd-mount to udev-extraconf/mount.shHongzhi.Song2018-09-171-17/+66
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Udev-extraconf works correctly with sysvinit in the aspect of automounting block devices. But it has a serious problem in case of systemd. Block devices automounted by udev is unaccessible to host space(out of udevd's private namespace). For example, we cannot format those block devices. e.g. root@qemux86:~# mkfs.ext4 /dev/sda1 mke2fs 1.43.8 (1-Jan-2018) /dev/sda1 contains a ext4 file system last mounted on Tue Apr 3 06:22:41 2018 Proceed anyway? (y,N) y /dev/sda1 is apparently in use by the system; will not make a filesystem here! Other distributions has no such problem, because they use a series of rules to manager block devices. Different types of block devices match different rules. But udev-extraconf just use one rule, automount.rules, which results in this problem. The 'systemd-mount' command is recommended by the systemd community to solve such problems. This patch makes use of 'systemd-mount' to solve the above problem. [YOCTO #12644] (From OE-Core rev: a0b3389c5afc23f622f793cbad8b4135093e6f08) (From OE-Core rev: 4af22800a7af4fcb80cafe08d982a4850d9dd2ad) Signed-off-by: Hongzhi.Song <hongzhi.song@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: introduce multiple blacklist files for more complex setupsJens Rehsack2016-01-061-1/+1
| | | | | | | | | | | | | | | | In cases where a target image wants prevent the recovery partition is mounted automatically, but the recovery partition identifier moves with the device (internal flash, sd card, usb stick, ...), device/machine dependend extra blacklists might be desired. The grep utility prints the file name for each match when there is more than one file to search. Add -h to suppress the prefixing of file names on output. (From OE-Core rev: 95fced137a46dc98863fe5af7be5cbce708602f2) Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Unmount SD card after ejectionYasir-Khan2014-08-152-3/+2
| | | | | | | | | | | | | | | | | | | Adds udev rule to unmount SD card partitions in case of improper ejection from card reader. When SD card is ejected from card reader without being unmounted first, kernel does not generate a REMOVE event, instead it generates a CHANGE event(only if polling is enabled /sys/module/block/parameters/events_dfl_poll_msecs) and we don't have any udev rule in automount.rules to handle this event,so partitions never get unmounted. Unmounting of partitions can be done if udev rules handle this CHANGE event. (From OE-Core rev: 140d188b3665f914396834168feeff6ffcb64d76) Signed-off-by: Abbas Raza <Abbas_Raza@mentor.com> Signed-off-by: Yasir-Khan <yasir_khan@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: fix the misuse of /run/mediaChen Qi2014-05-201-1/+1
| | | | | | | | | | | | | | | | | | | The error was introduced by the following commit. acfe3014d41de5e87cdbc58d0396349c6b9c3ffd udev-extraconf: update mount.sh to use /run/media instead of /media It accidently replaced 'device/media' by 'device/run/media' which causes error for live images to be unable to boot up correctly, complaining "Cannot find rootfs.img in /media/*". This patch fixes the above problem. (From OE-Core rev: 62ae16c40252f39ba28e072218d67f47b26b3535) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: update mount.sh to use /run/media instead of /mediaDenys Dmytriyenko2014-04-251-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This is done to work around the issue of auto-mounting block devices (i.e. SD cards) when root filesystem is still in read-only mode and creating /media/<device> mount-points by udev is not possible. That is due to udev (/etc/rcS.d/S03udev) getting started earlier than checkroot (/etc/rcS.d/S10checkroot.sh) gets a chance to re-mount the rootfs as read-write. Although, canonical FHS specifies /media/<device> as a mount point for removable media devices, the latest 2.3 version was released in 2004 and since then FreeDesktop/udisks and other tools adopted the new /run/media/<user>/<device> location. That was done to overcome read-only rootfs limitation, since /run is usually a tmpfs mounted partition, plus avoid name-clash between users. For our embedded systems environment we assume single-user operation and hence simplify mount point to just /run/media/<device>. But for proper per-user mounting to /run/media/<user>/<device>, some sort of session management is required along with the tool like udisks, that is out of scope of this simple udev-based auto-mounting. (From OE-Core rev: acfe3014d41de5e87cdbc58d0396349c6b9c3ffd) Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mount.sh: automount cdrom device even if no ID_FS_TYPE availableChen Qi2013-09-101-1/+5
| | | | | | | | | | | | | | | | | | This script was modified to check whether $ID_FS_TYPE is empty before automount, however, for cdrom devices on qemu, the ID_FS_TYPE is not set, yet the device should be mounted. Otherwise, when booting an iso image with runqemu, the boot process hangs at 'waiting for removable media'. This patch fixes this problem by first checking whether the block device is a cdrom. [YOCTO #4487] (From OE-Core rev: 2df21a3b27543df912a3ce05bef2415fae13cb7c) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: allow users in disk group to write vfat filesystemHongxu Jia2013-07-181-0/+11
| | | | | | | | | | | | | | | If filesystem type is vfat, change the ownership group to 'disk', and grant it with w/r/x permissions. The user which belongs to 'disk' group could write the storage. [YOCTO #4004] (From OE-Core rev: eeed0cebebc945bf62b29336b9df8e2c0a975538) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: blacklist /dev/dm-*Jackie Huang2013-07-051-0/+1
| | | | | | | | | | | | | | | Do not mount /dev/dm-* by default via udev, this is the default behavior for most distos and WRLinux4.x. This resolved a problem with the sanity test failing due to seeing the error while attempting to mount new logical volumes without fs. (From OE-Core rev: 9a6cf08afd81c95abf13e6cf5e43bb8cd777edd9) Signed-off-by: Xin Ouyang <Xin.Ouyang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Avoid mounting unknown filesystemsOtavio Salvador2013-04-281-1/+1
| | | | | | | | | | | | | | | | | | | Depending on kernel version used, the system can hung when trying to mount the extended partition (not the logical one) as it is a holder for other partitions and does not have a filesystem in it. To avoid this to happen we just mount partitions when these are using known filesystems so it does not try to mount a partition for an unsupported filesystem. Reported-by: Vladan Jovanovic <vladan.jovanovic@gmail.com> Reported-by: Leonardo Sandoval Gonzalez <b42214@freescale.com> (From OE-Core rev: 895c9685a7f95dc84786213f945895a504a16254) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Tested-by: Vladan Jovanovic <vladan.jovanovic@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Add -o silent to auto mount for mount.util-linuxSaul Wold2013-04-131-0/+5
| | | | | | | | | | | | | This will silence some of the noisy output from mount.util-linux and the kernel when trying to automount filesystems or devices. Busybox does not accept the silent option, it uses a loud option instead. [YOCTO #3935] (From OE-Core rev: be218292ee3f05afe47545aa8e1625452e0cd614) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Add rule adding input devices to input groupDarren Hart2013-04-041-0/+2
| | | | | | | | | | | | | | | | | Fixes [YOCTO 4164](2/3) Add all /dev/input/* devices to the input group with g+rw. This is needed for rootless X without adding a security hole by making the device o+rw. (From OE-Core rev: 66c9b46f987f3e4f1f9b7b11d1ae157897454f07) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Saul Wold <sgw@linux.intel.com> Cc: Radu Moisan <radu.moisan@intel.com> Cc: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Don't mount root filesystem under /mediaAndy Ross2012-10-271-2/+6
| | | | | | | | | | | | | | | The mount.sh handler attempts to prevent already-mounted filesystems from being mounted as dynamic/removable "/media". But it misses the case where the kernel has mounted the root filesystem (e.g. with "root=/dev/sda1"). In that situation, /proc/mounts has a device name of "/dev/root" instead of the proper $DEVNAME string exposed by udev. So we must also test the root filesystem device number vs. the $MAJOR/$MINOR udev tells us. (From OE-Core rev: 3543d0db691e82098c1da7bf12f43e0c57551a3d) Signed-off-by: Andy Ross <andy.ross@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: change LICENSE to MITMartin Jansa2012-09-041-339/+0
| | | | | | | | | | | | | | | * Original recipe added by RP in fc128ab1e4fec27d44cebfa690a9bc233eda0caf was saying GPL (later GPLv2) * COPYING.GPL was added to reflect that * Meta-oe has similar recipe with MIT license and even more scripts, so lets change LICENSE here too * Most code was derived from the meta-oe version or added to OE arguably under MIT and the MIT license makes most sense here (From OE-Core rev: 54a4a0b42d4515260841229d69f9cc43485bcb78) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: Merge with udev-extra-rules from meta-oeMartin Jansa2012-09-045-0/+180
| | | | | | | | | | | | | * Move parts of local.rules from udev to udev-extraconf * Move mount.sh and network.sh to udev-extraconf along with rule fragments * Add mount.blacklist to CONFFILES * Change PV to 1.0 and bump PR to provide upgrade path from meta-oe's udev-extra-rules including RREPLACE/RPROVIDES/RCONFLICTS trio (From OE-Core rev: 0ca3a7823e97c4e4af6e89d852f98d29ed6193d7) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: move mount.blacklist to udev-extraconf dirOtavio Salvador2012-01-031-0/+4
| | | | | | | (From OE-Core rev: bb7644b1e59fcffd0944b4f408dd90cfae7aa7a0) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev-extraconf: add license infoQing He2010-12-101-0/+339
Signed-off-by: Qing He <qing.he@intel.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-06 19:20:19 +0000