From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tejun Heo <tj@kernel•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Mans Rullgard <mans@mansr•com>,
Christian Lamparter <chunkeey@googlemail•com>
Subject: linux-next: build failure after merge of the libata tree
Date: Mon, 9 May 2016 10:14:27 +1000 [thread overview]
Message-ID: <20160509101427.4fd6fd36@canb.auug.org.au> (raw)
Hi Tejun,
After merging the libata tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/ata/sata_dwc_460ex.c:203:2: error: unknown field 'm_master' specified in initializer
.m_master = 1,
^
/home/sfr/next/next/drivers/ata/sata_dwc_460ex.c:204:2: error: unknown field 'p_master' specified in initializer
.p_master = 0,
^
/home/sfr/next/next/drivers/ata/sata_dwc_460ex.c: In function 'sata_dwc_dma_init_old':
/home/sfr/next/next/drivers/ata/sata_dwc_460ex.c:269:9: error: too few arguments to function 'dw_dma_probe'
return dw_dma_probe(hsdev->dma);
^
Caused by commit
30ee9d52f7a7 ("ata: sata_dwc_460ex: use "dmas" DT property to find dma channel")
I have used the libata tree from next-20160506 for today.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-05-09 0:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 0:14 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-06 14:08 linux-next: build failure after merge of the libata tree Stephen Rothwell
2022-01-06 23:58 ` Damien Le Moal
2022-01-07 0:17 ` Stephen Rothwell
2022-01-07 1:28 ` Damien Le Moal
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=20160509101427.4fd6fd36@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=chunkeey@googlemail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mans@mansr$(echo .)com \
--cc=tj@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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