From: Brian King <brking@linux.vnet.ibm.com>
To: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org, Jiri Kosina <trivial@kernel.org>,
Brian King <brking@us.ibm.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>
Subject: Re: [PATCH] ipr: trivial: fix small coding style issues
Date: Thu, 23 Aug 2012 15:01:27 -0500 [thread overview]
Message-ID: <50368C17.1010902@linux.vnet.ibm.com> (raw)
In-Reply-To: <1345670054-6757-1-git-send-email-klebers@linux.vnet.ibm.com>
On 08/22/2012 04:14 PM, Kleber Sacilotto de Souza wrote:
> Fixing small trivial coding style issues.
>
> Signed-off-by: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
> ---
> drivers/scsi/ipr.c | 66 ++++++++++++++++++++++++++--------------------------
> 1 files changed, 33 insertions(+), 33 deletions(-)
Acked-by: Brian King <brking@linux.vnet.ibm.com>
--
Brian King
Power Linux I/O
IBM Linux Technology Center
prev parent reply other threads:[~2012-08-23 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 21:14 [PATCH] ipr: trivial: fix small coding style issues Kleber Sacilotto de Souza
2012-08-23 20:01 ` Brian King [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=50368C17.1010902@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=JBottomley@parallels.com \
--cc=brking@us.ibm.com \
--cc=klebers@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=trivial@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.