From: "'Christoph Hellwig'" <hch@lst.de>
To: "Bagalkote, Sreenivas" <Sreenivas.Bagalkote@engenio.com>
Cc: 'Christoph Hellwig' <hch@lst.de>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] megaraid_sas: cleanup up queuecommand path
Date: Wed, 5 Oct 2005 18:25:53 +0200 [thread overview]
Message-ID: <20051005162553.GB3930@lst.de> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57060CD21C@exa-atlanta>
On Tue, Oct 04, 2005 at 06:56:55PM -0400, Bagalkote, Sreenivas wrote:
> Christoph,
>
> The patch looks fine to me. Thanks. But I would like to hold it until
> I can align my next internal release. I am in a code-freeze mode right
> now. Since this is a code cleanup rather than a fix, it would be great
> if I can release these patches at lock step with my internal ones to
> avoid maintaining different branches locally.
Sure, fine with me.
next prev parent reply other threads:[~2005-10-05 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 22:56 [PATCH] megaraid_sas: cleanup up queuecommand path Bagalkote, Sreenivas
2005-10-05 16:25 ` 'Christoph Hellwig' [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-04 18:41 Christoph Hellwig
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=20051005162553.GB3930@lst.de \
--to=hch@lst.de \
--cc=Sreenivas.Bagalkote@engenio.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;
as well as URLs for NNTP newsgroup(s).