From: Christoph Hellwig <hch@lst.de>
To: Oleg Drokin <green@namesys.com>
Cc: hch@lst.de, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: "[PATCH] devfs: switch over ubd to ->devfs_name" breaks ubd/sysfs
Date: Mon, 21 Apr 2003 14:18:45 +0200 [thread overview]
Message-ID: <20030421141845.A25822@lst.de> (raw)
In-Reply-To: <20030421155530.A7544@namesys.com>; from green@namesys.com on Mon, Apr 21, 2003 at 03:55:30PM +0400
On Mon, Apr 21, 2003 at 03:55:30PM +0400, Oleg Drokin wrote:
> Hello!
>
> The "[PATCH] devfs: switch over ubd to ->devfs_name" patch that was included into 2.5.68,
> have broken UML's ubd/sysfs interaction.
> Sysfs is very upset when something tries to register several devices with
> same name, so I was forced to use following patch.
> If this is wrong, then please explain to me why, and suggest the correct way of handling
> this situation.
Patch looks okay to me. But I'm still a bit confused about all
that fake_major stuff. Someone care to explain it?
next prev parent reply other threads:[~2003-04-21 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 11:55 "[PATCH] devfs: switch over ubd to ->devfs_name" breaks ubd/sysfs Oleg Drokin
2003-04-21 12:18 ` Christoph Hellwig [this message]
2003-04-21 12:30 ` Oleg Drokin
2003-04-21 12:34 ` Christoph Hellwig
2003-04-21 12:39 ` Oleg Drokin
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=20030421141845.A25822@lst.de \
--to=hch@lst.de \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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