From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
codalist@telemann.coda.cs.cmu.edu, coda@cs.cmu.edu,
Jan Harkes <jaharkes@cs.cmu.edu>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Praneeth Bajjuri <praneeth@ti.com>,
Paul Sokolovsky <paul.sokolovsky@linaro.org>,
Miklos Szeredi <mszeredi@suse.cz>,
Sumit Semwal <sumit.semwal@linaro.org>,
Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v2 2/2] scsi: aic7xxx: Fix build using bare-metal toolchain
Date: Thu, 30 Aug 2018 07:41:58 -0400 [thread overview]
Message-ID: <yq1efeg3wu1.fsf@oracle.com> (raw)
In-Reply-To: <20180829170015.7729-3-semen.protsenko@linaro.org> (Sam Protsenko's message of "Wed, 29 Aug 2018 20:00:15 +0300")
Sam,
> Bare-metal toolchains don't define __linux__, so aic7xxx build with
> bare-metal toolchain is broken. This driver codebase used to be
> partially shared with FreeBSD, but these days there is no point in
> keeping the compatibility around. So let's just drop FreeBSD related
> code and get rid of __linux__ checking in order to fix the build using
> bare-metal toolchains.
Applied to 4.20/scsi-queue, thank you!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-08-30 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 17:00 [PATCH v2 0/2] Fix allmodconfig build with bare-metal toolchain Sam Protsenko
2018-08-29 17:00 ` [PATCH v2 1/2] codafs: Fix build using " Sam Protsenko
2018-09-11 16:53 ` Sam Protsenko
2018-08-29 17:00 ` [PATCH v2 2/2] scsi: aic7xxx: " Sam Protsenko
2018-08-30 11:41 ` 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=yq1efeg3wu1.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=andy.shevchenko@gmail.com \
--cc=coda@cs.cmu.edu \
--cc=codalist@telemann.coda.cs.cmu.edu \
--cc=hch@infradead.org \
--cc=jaharkes@cs.cmu.edu \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=paul.sokolovsky@linaro.org \
--cc=praneeth@ti.com \
--cc=ruslan.bilovol@gmail.com \
--cc=semen.protsenko@linaro.org \
--cc=sumit.semwal@linaro.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