From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, akpm@digeo.com
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] cryptoloop
Date: Thu, 3 Jul 2003 00:57:54 +0200 (MEST) [thread overview]
Message-ID: <UTC200307022257.h62Mvsl26040.aeb@smtp.cwi.nl> (raw)
From Andrew.Morton@digeo.com Wed Jul 2 23:36:40 2003
> Now suppose one wants a large dev_t. Some people do.
<thumps table> 2.6 will support a large dev_t.
We need to make this happen.
Very well.
> Then several steps are needed. One of these steps
> is the addition of the mknod64 system call.
> That is a nice small isolated step - part of the necessary
> user space interface. It can be done independently of any
> other steps. It was submitted, but is not in the present
> kernel. Why not? I do not recall anybody pointing out problems.
This precisely illustrates my point.
mknod64() and several other dev_t patches (ext2 and ext3 support,
especially) have stalled in -mm for months. The reason why I have not
moved ahead with them is that I am waiting to see the rest of the work.
That is what they call a deadlock.
You asked a few times what parts could be submitted and I answered.
Because it could be that Al has different ideas, or that someone else gets
down and completes the work and wants to do it differently. I simply do
not know.
Neither do I. I just wait and see.
Andries
next reply other threads:[~2003-07-02 22:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 22:57 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-04 13:21 [PATCH] cryptoloop Andries.Brouwer
2003-07-04 13:28 ` Christoph Hellwig
2003-07-04 11:08 Andries.Brouwer
2003-07-04 12:13 ` Christoph Hellwig
2003-07-03 16:25 Andries.Brouwer
2003-07-03 16:31 ` Christoph Hellwig
2003-07-02 22:27 Andries.Brouwer
2003-07-02 21:00 Andries.Brouwer
2003-07-02 21:06 ` Greg KH
2003-07-02 21:31 ` Andrew Morton
2003-07-03 16:23 ` Christoph Hellwig
2003-07-02 19:42 Andries.Brouwer
2003-07-02 19:58 ` Andrew Morton
2003-07-02 18:44 Andries.Brouwer
2003-07-02 19:02 ` Andrew Morton
2003-07-02 19:16 ` Linus Torvalds
2003-07-02 19:20 ` Andrew Morton
2003-07-02 19:31 ` Linus Torvalds
2003-07-03 11:21 ` Jari Ruusu
2003-07-03 15:20 ` Andrew Morton
2003-07-03 17:29 ` Jari Ruusu
2003-07-03 17:38 ` Chris Friesen
2003-07-04 7:43 ` Jari Ruusu
2003-07-04 8:44 ` Andrew Morton
2003-07-04 9:41 ` Christoph Hellwig
2003-07-05 8:41 ` Jari Ruusu
2003-07-05 8:58 ` Andrew Morton
2003-07-05 9:00 ` Andre Hedrick
2003-07-05 9:10 ` Andre Hedrick
2003-07-05 17:16 ` James Morris
2003-07-05 17:20 ` Linus Torvalds
2003-07-08 12:43 ` Christoph Hellwig
2003-07-04 9:39 ` Christoph Hellwig
2003-07-03 16:20 ` Christoph Hellwig
2003-07-02 15:21 Andries.Brouwer
2003-07-02 17:16 ` Andrew Morton
2003-07-03 15:44 ` Christoph Hellwig
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=UTC200307022257.h62Mvsl26040.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).