From: "zhao, forrest" <forrest.zhao@intel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: htejun@gmail.com, liml@rtr.ca, ric@emc.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH v4] Snoop SET FEATURES - WRITE CACHE ENABLE/DISABLE command
Date: Mon, 12 Jun 2006 11:32:17 +0800 [thread overview]
Message-ID: <1150083137.5721.27.camel@forrest26.sh.intel.com> (raw)
In-Reply-To: <448CE1B6.8020706@garzik.org>
On Sun, 2006-06-11 at 23:38 -0400, Jeff Garzik wrote:
> zhao, forrest wrote:
> > Hi, Tejun
> >
> > Sorry, my brain turned dull after one-day work......
> > I should have fixed that in take 3.
> >
> > Thanks,
> > Forrest
> >
> > Signed-off-by: Forrest Zhao <forrest.zhao@intel.com>
>
> This looks pretty good to me. Please send out a v5 which re-diffs
> against the latest #upstream. The last pull from Tejun included some of
> the changes in your v4 patch (use of __scsi_add_device, etc.).
>
> Jeff
I sent out V5 20 minutes ago :)
Thanks,
Forrest
prev parent reply other threads:[~2006-06-12 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 8:49 [PATCH v4] Snoop SET FEATURES - WRITE CACHE ENABLE/DISABLE command zhao, forrest
2006-06-12 3:38 ` Jeff Garzik
2006-06-12 3:32 ` zhao, forrest [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=1150083137.5721.27.camel@forrest26.sh.intel.com \
--to=forrest.zhao@intel.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=ric@emc.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;
as well as URLs for NNTP newsgroup(s).