public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add <linux/kdev_t.h> to <linux/bio.h>
Date: Wed, 5 Jun 2002 16:42:01 -0700	[thread overview]
Message-ID: <20020605234201.GC709@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.33.0206021853030.1383-100000@penguin.transmeta.com> <20020605232220.GA709@opus.bloom.county> <20020606003420.A17872@flint.arm.linux.org.uk>

On Thu, Jun 06, 2002 at 12:34:20AM +0100, Russell King wrote:
> On Wed, Jun 05, 2002 at 04:22:20PM -0700, Tom Rini wrote:
> > The following add <linux/kdev_t.h> to <linux/bio.h>.
> > 
> > This is needed since bio_ioctl takes a kdev_t for its first argument.
> 
> This should be fixed by a patch I submitted earlier today (you're getting
> a build error in fs/mpage.c, right?)

Nope.  This was with that applied.  I'm breaking up mm.h, slightly,
right now and hit that.

> hch asked the very pertinent question though - why isn't kdev_t defined
> by linux/types.h ?

That is a good question...  Possibly because of the other stuff
associated with it.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

  reply	other threads:[~2002-06-05 23:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  1:56 Linux 2.5.20 Linus Torvalds
2002-06-03  3:06 ` 2.5.20 -- suspend.c still breaks the build (originally reported for 2.5.18) Miles Lane
2002-06-04 14:06   ` Pavel Machek
2002-06-03  3:18 ` [patch] i386 "General Options" - begone [take 2] Brad Hards
2002-06-03 22:42   ` Rusty Russell
2002-06-04 14:09   ` Pavel Machek
2002-06-04 22:05     ` Brad Hards
2002-06-02  5:16       ` Pavel Machek
2002-06-03 13:34 ` Oops Linux 2.5.20 Martin Dalecki
2002-06-03 14:06 ` [PATCH] 2.5.20 airo wireless - "I can't get no, compilation..." Martin Dalecki
2002-06-03 14:09 ` ]PATCH] 2.5.20 IDE 83 Martin Dalecki
2002-06-04 12:07   ` Jens Axboe
2002-06-04 15:30 ` [PATCH] 2.5.20 IDE 84 Martin Dalecki
2002-06-05 13:03 ` [PATCH] 2.5.20 IDE 85 Martin Dalecki
2002-06-05 14:17   ` Jens Axboe
2002-06-05 14:00     ` Martin Dalecki
2002-06-05 15:48       ` Jens Axboe
2002-06-05 15:52         ` Jens Axboe
2002-06-05 15:10           ` Martin Dalecki
2002-06-05 16:14             ` Jens Axboe
2002-06-05 15:26               ` Martin Dalecki
2002-06-05 18:02               ` Jeff Garzik
2002-06-06  7:17           ` Martin Dalecki
2002-06-05 16:36 ` [PATCH] Cleanup i386 <linux/init.h> abuses Tom Rini
2002-06-07 11:01   ` Pavel Machek
2002-06-07 19:19     ` Thunder from the hill
2002-06-07 19:26     ` Tom Rini
2002-06-05 23:22 ` [PATCH] Add <linux/kdev_t.h> to <linux/bio.h> Tom Rini
2002-06-05 23:34   ` Russell King
2002-06-05 23:42     ` Tom Rini [this message]
2002-06-06 18:33 ` [PATCH] Move vmalloc wrappers out of include/linux/vmalloc.h Tom Rini
2002-06-06 19:44 ` [PATCH] Remove <linux/mm.h> from <linux/vmalloc.h> Tom Rini
2002-06-06 21:02   ` [PATCH] More work on removing " Tom Rini
2002-06-06 21:21 ` [PATCH] Include <linux/gfp.h> directly instead of via <linux/mm.h> Tom Rini
2002-06-06 21:24 ` [PATCH] Remove numerous includes from <linux/mm.h> Tom Rini

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=20020605234201.GC709@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@transmeta.com \
    /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