From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Kashyap, Desai" <kashyap.desai@lsi.com>
Cc: linux-scsi@vger.kernel.org, Eric.Moore@lsi.com, Sathya.Prakash@lsi.com
Subject: Re: [PATCH 18/24] mpt fusion: [2.6.30-rc6] Code Cleanup patch
Date: Wed, 27 May 2009 17:53:43 +0000 [thread overview]
Message-ID: <1243446823.6067.40.camel@localhost.localdomain> (raw)
In-Reply-To: <20090522110832.GL16331@lsi.com>
On Fri, 2009-05-22 at 16:38 +0530, Kashyap, Desai wrote:
> +
> +#define mpt_sg_next sg_next
So everything in here looks vaguely OK (modulo a few over wrapped
prints) except this ... what's the point of adding this obfuscation?
James
prev parent reply other threads:[~2009-05-27 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 11:08 [PATCH 18/24] mpt fusion: [2.6.30-rc6] Code Cleanup patch Kashyap, Desai
2009-05-27 17:53 ` 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=1243446823.6067.40.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Eric.Moore@lsi.com \
--cc=Sathya.Prakash@lsi.com \
--cc=kashyap.desai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.