From: Dave Kleikamp <shaggy@austin.ibm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: reiserfs-dev@namesys.com, andrea@suse.de,
linux-kernel@vger.kernel.org, mauelshagen@sistina.com,
Holger Smolinski <HSmolinski@de.ibm.com>,
Horst Hummel <Horst.Hummel@de.ibm.com>
Subject: Re: [Jfs-discussion] Design-Question: end_that_request_* and bh->b_end_io hooks
Date: Wed, 25 Jul 2001 16:47:39 -0500 [thread overview]
Message-ID: <3B5F3E7B.6C7281AC@austin.ibm.com> (raw)
In-Reply-To: <200107252104.f6PL4Kn03703@shaggy.austin.ibm.com>
Oops! I shouldn't have sent the patch to everyone on the cc list. I
wasn't paying attention. I'm sorry everyone!
Dave Kleikamp
next prev parent reply other threads:[~2001-07-25 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 17:20 Design-Question: end_that_request_* and bh->b_end_io hooks Carsten Otte
2001-07-25 17:24 ` tpepper
2001-07-25 21:04 ` [Jfs-discussion] " Dave Kleikamp
2001-07-25 21:47 ` Dave Kleikamp [this message]
2001-07-26 6:40 ` Jens Axboe
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=3B5F3E7B.6C7281AC@austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=HSmolinski@de.ibm.com \
--cc=Horst.Hummel@de.ibm.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mauelshagen@sistina.com \
--cc=reiserfs-dev@namesys.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