From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Ewan D. Milne" <emilne@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [TRIVIAL PATCH 0/2] Fix warnings in kernel build
Date: Mon, 26 Aug 2013 21:53:05 +0400 [thread overview]
Message-ID: <1377539585.7961.5.camel@dabdike> (raw)
In-Reply-To: <1377536800-2298-1-git-send-email-emilne@redhat.com>
On Mon, 2013-08-26 at 13:06 -0400, Ewan D. Milne wrote:
> From: "Ewan D. Milne" <emilne@redhat.com>
>
> The patch to add uevents for certain Unit Attention codes
> had a couple of problems which were found by a kbuild test robot.
> Sorry about that, I will be more careful next time.
I already did both of these based on Fengguang's checker results ...
James
prev parent reply other threads:[~2013-08-26 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 17:06 [TRIVIAL PATCH 0/2] Fix warnings in kernel build Ewan D. Milne
2013-08-26 17:06 ` [TRIVIAL PATCH 1/2] scsi: Add missing @sdev parameter description to scsi_report_sense() Ewan D. Milne
2013-08-26 17:06 ` [TRIVIAL PATCH 2/2] scsi: Remove unused variable "flags" from scsi_report_sense() Ewan D. Milne
2013-08-26 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=1377539585.7961.5.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=emilne@redhat.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