Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] udev 124: add cache invalidation logic on kernel change or its bootargs/cmdline
Date: Sat, 18 Apr 2009 11:31:38 +0200	[thread overview]
Message-ID: <gsc6lq$rsp$1@ger.gmane.org> (raw)
In-Reply-To: <20090416163353.GG17629@smtp.west.cox.net>

On 16-04-09 18:33, Tom Rini wrote:
> On Tue, Apr 14, 2009 at 07:49:58PM -0400, Denys Dmytriyenko wrote:
>
>> Signed-off-by: Denys Dmytriyenko<denis@denix.org>
>> ---
>>   recipes/udev/udev-124/init |   10 +++++++++-
>>   1 files changed, 9 insertions(+), 1 deletions(-)
>
> So, for making it optional, how about adding something to /etc/default
> to enable / disable dev caching all together?  And, I believe
> /proc/atags would just be cp /proc/atags /tmp/atags || touch /tmp/atags.

Do we really want atags in there? As the name says, they are ARM TAGs, 
and only when kexec is enabled. Does it buy us anything over /proc/cmdline?

regards,

Koen





  reply	other threads:[~2009-04-18  9:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 23:46 [RFC] Invalidating udev cache Denys Dmytriyenko
2009-04-14 23:49 ` [PATCH] udev 124: add cache invalidation logic on kernel change or its bootargs/cmdline Denys Dmytriyenko
2009-04-15  6:47   ` Koen Kooi
2009-04-15  6:54     ` Holger Schurig
2009-04-16  0:06       ` Denys Dmytriyenko
2009-04-16 12:34         ` Otavio Salvador
2009-04-16 13:04           ` Koen Kooi
2009-04-16 16:33   ` Tom Rini
2009-04-18  9:31     ` Koen Kooi [this message]
2009-04-18 17:56       ` Tom Rini
2009-04-18 18:56         ` Mike (mwester)

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='gsc6lq$rsp$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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