All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Joe Thornber <thornber@sistina.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@zip.com.au>,
	Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 3/6] dm: decimal device num sscanf
Date: Thu, 31 Jul 2003 17:14:43 +0100	[thread overview]
Message-ID: <20030731171443.A23456@infradead.org> (raw)
In-Reply-To: <20030731152454.GA394@fib011235813.fsnet.co.uk>; from thornber@sistina.com on Thu, Jul 31, 2003 at 04:24:54PM +0100

On Thu, Jul 31, 2003 at 04:24:54PM +0100, Joe Thornber wrote:
> > > It's in there to match the output from 'dmsetup table'.  I'm not sure
> > > anyone uses it, but I'd still like to keep it so that 2.4 and 2.6 stay
> > > in sync.
> > 
> > Please do the matching from dev_t to pathname in userspace.

So why do you do it in kernel again?


  reply	other threads:[~2003-07-31 16:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 10:45 2.6.0-test2 device mapper patchset Joe Thornber
2003-07-31 10:48 ` [Patch 1/6] dm: don't use MODULE_PARM Joe Thornber
2003-07-31 10:49 ` [Patch 2/6] dm: remove blk.h include Joe Thornber
2003-07-31 10:49 ` [Patch 3/6] dm: decimal device num sscanf Joe Thornber
2003-07-31 15:04   ` Christoph Hellwig
2003-07-31 15:13     ` Joe Thornber
2003-07-31 15:20       ` Christoph Hellwig
2003-07-31 15:24         ` Joe Thornber
2003-07-31 16:14           ` Christoph Hellwig [this message]
2003-07-31 16:27             ` Joe Thornber
2003-08-02 16:54               ` Christoph Hellwig
2003-07-31 16:13       ` Christophe Saout
2003-07-31 10:50 ` [Patch 4/6] dm: 64 bit ioctl fixes Joe Thornber
2003-07-31 10:51 ` [Patch 5/6] dm: missing #include Joe Thornber
2003-07-31 10:51 ` [Patch 6/6] dm: use sector_div() Joe Thornber
2003-07-31 10:57 ` [Patch 7/6 (so I can't count)] dm: resume() name clash Joe Thornber

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=20030731171443.A23456@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thornber@sistina.com \
    --cc=torvalds@osdl.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.