From: Greg KH <gregkh@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org, kay.sievers@vrfy.org
Subject: Re: partition sysfs OOPS in current GIT
Date: Wed, 6 Feb 2008 16:07:45 -0800 [thread overview]
Message-ID: <20080207000745.GB16389@suse.de> (raw)
In-Reply-To: <20080206155749.ce1fcd25.akpm@linux-foundation.org>
On Wed, Feb 06, 2008 at 03:57:49PM -0800, Andrew Morton wrote:
> > How is it working for anyone else then? sparc64 isn't doing anything
> > "odd" with it's block devices, is it?
> >
> > > I'm pretty sure the following changeset is to blame:
> > >
> > > commit edfaa7c36574f1bf09c65ad602412db9da5f96bf
> > > Author: Kay Sievers <kay.sievers@vrfy.org>
> > > Date: Mon May 21 22:08:01 2007 +0200
> > >
> > > Driver core: convert block from raw kobjects to core devices
> > >
> > > This moves the block devices to /sys/class/block. It will create a
> > > flat list of all block devices, with the disks and partitions in one
> > > directory. For compatibility /sys/block is created and contains symlinks
> > > to the disks.
> >
> > So I'm guessing if you revert this it works?
>
> Going offtopic here...
>
> The patch was committed to mainline last week and it has a git timestamp
> from eight months ago. When you received the original email from Kay.
>
> But the patch changed in that time period. This doesn't seem right?
The patch did change over time, but not that much, minor bugfixes for
it. I didn't think to update the original date in the quilt file,
sorry. It was in -mm for quite a while, so I thought it got a good
enough testing period.
I'll try to remember to update the timestamp on patches that get
updated, it's a pretty rare thing for my patchflow, shouldn't be hard to
remember.
thanks,
greg k-h
next prev parent reply other threads:[~2008-02-07 0:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:26 partition sysfs OOPS in current GIT David Miller
2008-02-06 23:31 ` Greg KH
2008-02-06 23:37 ` David Miller
2008-02-06 23:48 ` David Miller
2008-02-06 23:59 ` Greg KH
2008-02-07 0:02 ` David Miller
2008-02-07 0:09 ` Greg KH
2008-02-07 0:29 ` David Miller
2008-02-07 4:06 ` David Miller
2008-02-07 5:47 ` Greg KH
2008-02-07 6:05 ` David Miller
2008-02-07 6:38 ` Greg KH
2008-02-07 6:38 ` David Miller
2008-02-07 6:42 ` Greg KH
2008-02-07 6:39 ` David Miller
2008-02-07 6:58 ` Greg KH
2008-02-07 7:00 ` Greg KH
2008-02-07 7:11 ` David Miller
2008-02-07 7:18 ` Greg KH
2008-02-07 7:33 ` David Miller
2008-02-07 7:43 ` Greg KH
2008-02-07 7:20 ` Greg KH
2008-02-07 7:24 ` David Miller
2008-02-07 7:42 ` Greg KH
2008-02-07 6:44 ` Greg KH
2008-02-07 6:42 ` David Miller
2008-02-06 23:57 ` Andrew Morton
2008-02-07 0:07 ` Greg KH [this message]
2008-02-06 23:42 ` Oops figures Jan Engelhardt
2008-02-06 23:42 ` Jan Engelhardt
2008-02-06 23:47 ` David Miller
2008-02-06 23:47 ` David Miller
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=20080207000745.GB16389@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kay.sievers@vrfy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.