public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Prakash, Sathya" <Sathya.Prakash@lsi.com>
Cc: linux-scsi@vger.kernel.org, "Moore, Eric" <Eric.Moore@lsi.com>
Subject: RE: [PATCH 1/3] mpt fusion: Request I/O resources only whenrequired
Date: Sat, 09 Feb 2008 11:34:34 -0600	[thread overview]
Message-ID: <1202578474.4254.22.camel@localhost.localdomain> (raw)
In-Reply-To: <5AE055B67BB5764693E2900C7E3699BEFB1C5C@pamail.ad.lsil.com>

On Sun, 2008-02-10 at 01:26 +0800, Prakash, Sathya wrote:
> Thanks James for pointing the missing of checkpatch.pl check. I will do
> it before submitting the future patches.

Great, thanks ... I still haven't seen PATCH 2/3 in this series, by the
way.

James



      reply	other threads:[~2008-02-09 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 17:26 [PATCH 1/3] mpt fusion: Request I/O resources only whenrequired Prakash, Sathya
2008-02-09 17:34 ` James Bottomley [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=1202578474.4254.22.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Eric.Moore@lsi.com \
    --cc=Sathya.Prakash@lsi.com \
    --cc=linux-scsi@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