From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: <shiju.jose@huawei.com>
Cc: <martin.petersen@oracle.com>, <jejb@linux.vnet.ibm.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<john.garry@huawei.com>, <xuwei5@hisilicon.com>
Subject: Re: [PATCH 1/1] scsi: hisi_sas: fix for the build error log_non_standard_event undefined
Date: Tue, 31 Oct 2017 12:33:02 -0400 [thread overview]
Message-ID: <yq1zi879t1d.fsf@oracle.com> (raw)
In-Reply-To: <3f14f745-6fdf-4948-85bb-d21d565dbcab@huawei.com> (shiju jose's message of "Tue, 31 Oct 2017 12:25:51 +0000")
Shiju,
> This patch fix the build error log_non_standard_event undefined
> for the i386 build for COMPILE_TEST.
This is messy. You have one patch addressing build problems in two
different patches. This breaks our ability to bisect.
I combined the ECC and AXI patches into one and then added the build fix
on top. Really hope that works.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-10-31 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:25 [PATCH 1/1] scsi: hisi_sas: fix for the build error log_non_standard_event undefined shiju.jose
2017-10-31 16:33 ` Martin K. Petersen [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=yq1zi879t1d.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=shiju.jose@huawei.com \
--cc=xuwei5@hisilicon.com \
/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