public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: Andries.Brouwer@cwi.nl
Cc: alan@lxorguk.ukuu.org.uk, sdake@mvista.com, dougg@torque.net,
	kurt@garloff.de, linux-kernel@vger.kernel.org
Subject: Re: 32bit dev_t
Date: Fri, 24 Jan 2003 17:51:08 -0800	[thread overview]
Message-ID: <20030125015108.GN20972@ca-server1.us.oracle.com> (raw)
In-Reply-To: <UTC200301242204.h0OM4jU09451.aeb@smtp.cwi.nl>

On Fri, Jan 24, 2003 at 11:04:45PM +0100, Andries.Brouwer@cwi.nl wrote:
> Once or twice a year I build a kernel with 32bit or 64bit dev_t.
> Every now and then submit a few patches so that doing so
> remains easy. The last real change was the change in prototype
> of the VFS *_mknod functions.

	It's good to know that the actual changes are small, but I was
specifically wondering what the status was as far as inclusion.  If
there are issues, what are they?  Etc.

Joel

-- 

"In the arms of the angel, fly away from here,
 From this dark, cold hotel room and the endlessness that you fear.
 You are pulled from the wreckage of your silent reverie.
 In the arms of the angel, may you find some comfort here."

Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2003-01-25  1:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 22:04 32bit dev_t Andries.Brouwer
2003-01-25  1:51 ` Joel Becker [this message]
2003-02-03 18:21 ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2003-01-21 19:50 Joel Becker
2003-01-21 21:29 ` Steven Dake
2003-01-21 21:56   ` Joel Becker
2003-01-21 22:21     ` Jeff Garzik
2003-01-21 22:33   ` Alan

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=20030125015108.GN20972@ca-server1.us.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dougg@torque.net \
    --cc=kurt@garloff.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdake@mvista.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