From: Linus Torvalds <torvalds@osdl.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: brugolsky@telemetry-investments.com, SteveD@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfs client O_DIRECT oops
Date: Mon, 28 Feb 2005 17:17:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0502281716490.25732@ppc970.osdl.org> (raw)
In-Reply-To: <20050228170016.0c26a109@localhost.localdomain>
On Mon, 28 Feb 2005, Pete Zaitcev wrote:
>
> This is how I think it should have been fixed:
Since this seems a cleanup, I'll drop it for now. Can you re-send after
2.6.11 (or forward it to the nfs people) so that it gets cleaned up at
some point? I do agree that your patch seems to be cleaner.
Linus
prev parent reply other threads:[~2005-03-01 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42236AC6.6000609@RedHat.com>
2005-03-01 1:00 ` Pete Zaitcev
2005-03-01 1:17 ` Linus Torvalds [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=Pine.LNX.4.58.0502281716490.25732@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=SteveD@redhat.com \
--cc=brugolsky@telemetry-investments.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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
all inboxes | Powered by JetHome®