From: Daniel Hellstrom <daniel@gaisler.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (sparc-current tree related)
Date: Thu, 31 Mar 2011 15:46:27 +0200 [thread overview]
Message-ID: <4D9485B3.5060306@gaisler.com> (raw)
In-Reply-To: <20110330.211044.212408233.davem@davemloft.net>
David Miller wrote:
>From: Stephen Rothwell <sfr@canb.auug.org.au>
>Date: Thu, 31 Mar 2011 13:01:27 +1100
>
>
>
>>Hi all,
>>
>>After merging the final tree, today's linux-next build (powerpc
>>allyesconfig) failed like this:
>>
>>drivers/tty/serial/apbuart.c: In function 'apbuart_probe':
>>drivers/tty/serial/apbuart.c:568: error: 'struct pdev_archdata' has no member named 'irqs'
>>
>>Caused by commit 10544f128c33 ("sparc32, leon: APBUART driver must use
>>archdata to get IRQ number").
>>
>>I have reverted that commit for today (and commit c897dcf6311e
>>"sparc32,leon: Fixed APBUART frequency detection" that conflicts with the
>>revert).
>>
>>
>
>Thanks, I'll make apbuart depend upon sparc to fix this.
>
>
Thanks all.
next prev parent reply other threads:[~2011-03-31 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 2:01 linux-next: build failure after merge of the final tree (sparc-current tree related) Stephen Rothwell
2011-03-31 4:10 ` David Miller
2011-03-31 13:46 ` Daniel Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-03 3:53 Stephen Rothwell
2011-06-03 5:20 ` David Miller
2011-06-03 7:42 ` Daniel Hellstrom
2011-06-03 8:14 ` David Miller
2011-06-03 12:26 ` Daniel Hellstrom
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=4D9485B3.5060306@gaisler.com \
--to=daniel@gaisler.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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