From: Mark Brown <broonie@kernel.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "lkp@intel.com" <lkp@intel.com>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: [linux-next:master 1837/11710] sh4-linux-ld: cannot find drivers/spi/.tmp_gl_spi-mux.o: No such file or directory
Date: Wed, 25 Mar 2020 20:32:44 +0000 [thread overview]
Message-ID: <20200325203244.GD12169@sirena.org.uk> (raw)
In-Reply-To: <3ec603f5379aafd36f80490ef78108b225eac030.camel@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On Wed, Mar 25, 2020 at 08:30:16PM +0000, Chris Packham wrote:
> On Thu, 2020-03-26 at 01:38 +0800, kbuild test robot wrote:
> > rm: cannot remove 'drivers/spi/.tmp_gl_spi-mux.o': No such file or
> > directory
> > rm: cannot remove 'drivers/spi/.tmp_mx_spi-mux.o': No such file or
> > directory
> I attempted to reproduce this. The sh4 toolchain was unhappy with my
> system (missing libisl.so.22). I bodged something together and got
> errors like this all over the place. I also tried the previous commit
> and still got the same errors.
I'm not overly worried about it TBH - it looks like either an issue with
the architecture or an infrastructure issue, this is plain C code not
doing anything fancy and if this were an error in the code I'd expect
that other architectures would be seeing similar problems.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-25 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202003260124.NDYYFnCI%lkp@intel.com>
2020-03-25 20:30 ` [linux-next:master 1837/11710] sh4-linux-ld: cannot find drivers/spi/.tmp_gl_spi-mux.o: No such file or directory Chris Packham
2020-03-25 20:32 ` Mark Brown [this message]
2020-03-26 0:21 ` [kbuild-all] " Rong Chen
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=20200325203244.GD12169@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=andy.shevchenko@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).