From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Hannes Reinecke <hare@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the libata tree
Date: Fri, 7 Jan 2022 01:08:32 +1100 [thread overview]
Message-ID: <20220107010832.42c93c30@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
Hi all,
After merging the libata tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/ata/pata_cs5535.c:26:10: fatal error: asm/msr.h: No such file or directory
26 | #include <asm/msr.h>
| ^~~~~~~~~~~
Caused by commit
39d0a5fc445a ("ata: pata_cs5535: add compile test support")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-01-06 14:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 14:08 Stephen Rothwell [this message]
2022-01-06 23:58 ` linux-next: build failure after merge of the libata tree Damien Le Moal
2022-01-07 0:17 ` Stephen Rothwell
2022-01-07 1:28 ` Damien Le Moal
-- strict thread matches above, loose matches on Subject: below --
2016-05-09 0:14 Stephen Rothwell
2015-09-17 4:03 Stephen Rothwell
2015-09-17 11:14 ` Luis de Bethencourt
2014-04-24 1:17 Stephen Rothwell
2014-04-24 12:25 ` Tejun Heo
2014-02-26 2:55 Stephen Rothwell
2014-02-26 13:49 ` Tejun Heo
2013-08-27 2:50 Stephen Rothwell
2013-08-27 5:52 ` Aaron Lu
2013-08-27 18:09 ` Tejun Heo
2013-08-19 1:54 Stephen Rothwell
2013-08-19 3:18 ` Terry Suereth
2013-08-19 13:40 ` Tejun Heo
2012-07-02 2:10 Stephen Rothwell
2012-07-02 2:19 ` huang ying
2010-08-18 0:40 Stephen Rothwell
2010-08-18 0:46 ` Gwendal Grignou
2010-08-19 20:15 ` Jeff Garzik
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=20220107010832.42c93c30@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.