public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Hanna V Linder <hannal@us.ibm.com>,
	Andrew Morton <akpm@zip.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: [CFT][PATCH] Re: 2.5.11 breakage
Date: Tue, 30 Apr 2002 11:00:43 +0200	[thread overview]
Message-ID: <3CCE5D3B.40207@evision-ventures.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0204291806280.5397-100000@weyl.math.psu.edu>

BTW.> Is anyone of you looking at the folding of
the contents of blk_dev[major] (custom request queue information)
in to struct block_device from fs.h, where it naturally belongs?


      parent reply	other threads:[~2002-04-30 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <390625259.1020069198@[10.10.2.2]>
2002-04-29 22:18 ` [CFT][PATCH] Re: 2.5.11 breakage Alexander Viro
2002-04-29 23:03   ` Hanna Linder
2002-04-30  9:00   ` Martin Dalecki [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=3CCE5D3B.40207@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=akpm@zip.com.au \
    --cc=hannal@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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