From: Oleg Drokin <green@namesys.com>
To: Christoph Hellwig <hch@lst.de>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Cc: jdike@karaya.com, user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH] devfs_mk_symlink simplification
Date: Mon, 24 Mar 2003 10:37:01 +0300 [thread overview]
Message-ID: <20030324103701.A22971@namesys.com> (raw)
In-Reply-To: <20030324103255.A20753@namesys.com>
Hello!
On Mon, Mar 24, 2003 at 10:32:55AM +0300, Oleg Drokin wrote:
> On Sat, Mar 22, 2003 at 06:39:38PM +0100, Christoph Hellwig wrote:
> > All devfs_mk_symlink arguments except the from and to strings are
> > unused. Bring the prototype in shape.
> This patch is needed in UML subtree now:
Argh, this patch is only relevant to patched Jeff's tree, everybody else
please ignore it.
Bye,
Oleg
prev parent reply other threads:[~2003-03-24 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 17:39 [PATCH] devfs_mk_symlink simplification Christoph Hellwig
2003-03-24 7:32 ` Oleg Drokin
2003-03-24 7:37 ` Oleg Drokin [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=20030324103701.A22971@namesys.com \
--to=green@namesys.com \
--cc=hch@lst.de \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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