linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: htejun@gmail.com, hare@suse.de, axboe@suse.de, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/6] The redefinition of ahci_start_engine()	andahci_stop_engine()
Date: Wed, 19 Jul 2006 16:47:34 -0400	[thread overview]
Message-ID: <44BE9A66.9020103@pobox.com> (raw)
In-Reply-To: <1152769112.7132.327.camel@forrest26.sh.intel.com>

applied patch 1

For the future, please make sure to follow rule #1 of 
http://linux.yyz.us/patch-format.html by including a subsystem name in 
your email subject lines, i.e.

ok:

	[PATCH 1/6] redefinition of ...

better:

	[PATCH 1/6] libata: redefinition of...

or:

	[PATCH 1/6] ahci: redefinition of...



      reply	other threads:[~2006-07-19 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  5:38 [PATCH 1/6] The redefinition of ahci_start_engine() andahci_stop_engine() zhao, forrest
2006-07-19 20:47 ` Jeff Garzik [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=44BE9A66.9020103@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=axboe@suse.de \
    --cc=forrest.zhao@intel.com \
    --cc=hare@suse.de \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.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).