From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] udev: also use /proc/devices to invalidate devcache
Date: Fri, 11 Feb 2011 21:21:18 +0100 [thread overview]
Message-ID: <ij45nu$678$1@dough.gmane.org> (raw)
In-Reply-To: <1297452931-19486-1-git-send-email-denis@denix.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11-02-11 20:35, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko <denys@ti.com>
>
> * Besides checking for kernel version, bootargs or cmdline changes between
> reboots, also consider changes in /proc/devices to invalidate device cache.
>
> Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Acked-by: Koen Kooi <k-kooi@ti.com>
FWIW, to make everything work properly newer udevs might need a change
in the trigger script to explicitly use --action=add, but I need to run
some more tests.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNVZo+MkyGM64RGpERAj97AJ9G4UOkQ9suecrPe0GvI7en+sRq0wCfbIX+
FieAuvTwv3YKyCBJk9ckaU4=
=iC0+
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-02-11 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 19:35 [PATCH] udev: also use /proc/devices to invalidate devcache Denys Dmytriyenko
2011-02-11 20:21 ` Koen Kooi [this message]
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='ij45nu$678$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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