From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21rc7-mm1 usb/sysfs oops.
Date: Tue, 1 May 2007 17:21:28 -0400 [thread overview]
Message-ID: <20070501212128.GI2843@redhat.com> (raw)
In-Reply-To: <20070501135552.ab54be25.akpm@linux-foundation.org>
On Tue, May 01, 2007 at 01:55:52PM -0700, Andrew Morton wrote:
> Unfortunately rc7-mm1 and rc7-mm2 had dodgy-now-dropped sysfs changes in
> it, so this might be a consequence of that.
>
> > No more being a smart-ass for me today.
>
> Would be good to test mainline instead, and/or -mm when Tejun's new sysfs
> patches appear. And cc linux-usb-devel and linux-scsi when it goes boom.
2.6.21 seems to survive.
Though replugging is treated as a new device, so it never reconstructs
the 'array'. Hmm, udev removed /dev/sdd when I removed the stick,
and on reinsertion created it /dev/sdf. How helpful of it. Hrmph.
udev sillies aside, it seems to behave as expected.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2007-05-01 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 18:23 2.6.21rc7-mm1 usb/sysfs oops Dave Jones
2007-05-01 20:55 ` Andrew Morton
2007-05-01 21:21 ` Dave Jones [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=20070501212128.GI2843@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.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