From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Hannes Reinecke <hare@suse.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aic7xxx: fix firmware build with O=path
Date: Mon, 24 Jul 2017 14:14:13 -0700 [thread overview]
Message-ID: <20170724141413.151dc05d@cakuba.netronome.com> (raw)
In-Reply-To: <5cf07bda-1bb8-4c71-58ad-d1af492b6c71@suse.com>
On Mon, 24 Jul 2017 09:00:41 +0200, Hannes Reinecke wrote:
> On 07/21/2017 08:51 PM, Jakub Kicinski wrote:
> > On Tue, 18 Jul 2017 18:58:34 -0700, Jakub Kicinski wrote:
> >> Building firmware with O=path was apparently broken in aic7 for ever.
> >> Message of the previous commit to the Makefile (from 2008) mentions
> >> this unfortunate state of affairs already. Fix this, mostly to make
> >> randconfig builds more reliable.
> >>
> >> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> >
> > Gentle ping :) Hannes, are you still maintaining aic7xxx?
> >
> Yes, I do.
>
> Patch looks reasonable; Kconfig is still black magic to me, though :-)
To me as well, but is seems to work fine in my tests :)
> Reviewed-by: Hannes Reinecke <hare@suse.com>
Thanks!
next prev parent reply other threads:[~2017-07-24 21:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 1:58 [PATCH] aic7xxx: fix firmware build with O=path Jakub Kicinski
2017-07-21 18:51 ` Jakub Kicinski
2017-07-24 7:00 ` Hannes Reinecke
2017-07-24 21:14 ` Jakub Kicinski [this message]
2017-07-25 2:07 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2017-06-29 4:17 Jakub Kicinski
2017-07-04 0:29 ` Jakub Kicinski
2017-07-19 1:35 ` Jakub Kicinski
2017-07-19 1:45 ` Martin K. Petersen
2017-07-19 1:52 ` Jakub Kicinski
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=20170724141413.151dc05d@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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