From: Greg KH <gregkh@linuxfoundation.org>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
codalist@coda.cs.cmu.edu, coda@cs.cmu.edu,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Praneeth Bajjuri <praneeth@ti.com>
Subject: Re: [PATCH v2] codafs: Fix build using bare-metal toolchain
Date: Tue, 30 Oct 2018 07:34:08 +0100 [thread overview]
Message-ID: <20181030063408.GA26627@kroah.com> (raw)
In-Reply-To: <CAKaJLVvpNZW2a+3xc7PE0+iU1nm39A7PEjCu8F9ijrT+wEXOag@mail.gmail.com>
On Mon, Oct 29, 2018 at 10:05:49PM +0200, Sam Protsenko wrote:
> Hi Greg,
>
> On Mon, Oct 29, 2018 at 10:03 PM, Sam Protsenko
> <semen.protsenko@linaro.org> wrote:
> > The kernel is self-contained project and can be built with bare-metal
> > toolchain. But bare-metal toolchain doesn't define __linux__. Because of
> > this u_quad_t type is not defined when using bare-metal toolchain and
> > codafs build fails. This patch fixes it by defining u_quad_t type
> > unconditionally.
> >
> > Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
> > ---
>
> Can you please pull this one, if this applicable? I sent it a while
> ago, but I guess it got lost in mailing list. It might be also
> applicable to stable branch (as it fixes allmodconfig build for ARM
> with bare-metal toolchain).
Why are you asking me? I'm not the maintainer of this file :(
confused,
greg k-h
next prev parent reply other threads:[~2018-10-30 6:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 20:03 [PATCH v2] codafs: Fix build using bare-metal toolchain Sam Protsenko
2018-10-29 20:05 ` Sam Protsenko
2018-10-29 20:08 ` Andy Shevchenko
2018-10-30 6:34 ` Greg KH [this message]
2018-10-30 12:01 ` Sam Protsenko
2018-10-30 13:04 ` Jan Harkes
2018-10-30 18:33 ` Sam Protsenko
2018-10-30 18:39 ` Andy Shevchenko
2018-11-23 20:07 ` Andy Shevchenko
2018-11-26 14:35 ` Sam Protsenko
-- strict thread matches above, loose matches on Subject: below --
2018-10-30 20:27 Sam Protsenko
2018-11-21 16:31 ` Sam Protsenko
2018-11-21 16:41 ` Andy Shevchenko
2018-11-21 16:57 ` Christoph Hellwig
2018-11-21 18:10 ` Jan Harkes
2018-11-21 19:36 ` Sam Protsenko
2018-11-21 19:39 ` Sam Protsenko
2018-11-21 22:48 ` Jan Harkes
2019-01-09 15:45 ` Sam Protsenko
2018-11-22 11:32 ` Andy Shevchenko
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=20181030063408.GA26627@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=coda@cs.cmu.edu \
--cc=codalist@coda.cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=semen.protsenko@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