All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the rtc tree
Date: Tue, 11 Apr 2017 17:52:20 +1000	[thread overview]
Message-ID: <20170411175220.43cd5280@canb.auug.org.au> (raw)
In-Reply-To: <20170411055509.o2ob2z3kavteykqh@piout.net>

Hi Alexandre,

On Tue, 11 Apr 2017 07:55:09 +0200 Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
>
> On 11/04/2017 at 10:22:38 +1000, Stephen Rothwell wrote:
> > 
> > On Mon, 10 Apr 2017 09:45:45 +0200 Hans de Goede <hdegoede@redhat.com> wrote:  
> > >
> > > On 10-04-17 08:04, Stephen Rothwell wrote:  
> > > >
> > > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig)
> > > > failed like this:
> > > >
> > > > ERROR: "legacy_pic" [drivers/rtc/rtc-cmos.ko] undefined!
> > > >
> > > > Caused by commit
> > > >
> > > >   d3e3a65c6a96 ("rtc: cmos: Do not assume irq 8 for rtc when there are no legacy irqs")
> > > >
> > > > "legacy_pic" is not exported to modules.
> > > >
> > > > I have used the rtc tree from next-20170407 for today.    
> > > 
> > > I already send out a patch to fix this yesterday. I've attached a copy.  
> > 
> > I will add that to linux-next today and will drop it when Alexandre
> > adds it (or some other fix).
> 
> I think the x86 maintainers will take it as it is fairly independent.

But it is a fix for a build failure caused by a commit in your tree ...
so you should probably get an ack from the x86 maintainers and add it
to your tree.  Or do some other fix in your tree.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-04-11  7:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  6:04 linux-next: build failure after merge of the rtc tree Stephen Rothwell
2017-04-10  7:45 ` Hans de Goede
2017-04-11  0:22   ` Stephen Rothwell
2017-04-11  5:55     ` Alexandre Belloni
2017-04-11  7:52       ` Stephen Rothwell [this message]
2017-04-14 10:09         ` Alexandre Belloni
2017-04-14 16:33           ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-10-16  4:15 Stephen Rothwell
2023-10-16  4:34 ` Alexandre Belloni
2023-10-16  7:11 ` Uwe Kleine-König
2021-09-27  3:10 Stephen Rothwell
2021-09-27  7:16 ` Romain Perier
2021-08-10  5:54 Stephen Rothwell
2020-03-16  5:15 Stephen Rothwell
2020-03-16  6:58 ` Ran Bi
2020-03-16 10:31   ` Alexandre Belloni
2019-10-04  4:37 Stephen Rothwell
2019-02-11  5:24 Stephen Rothwell
2019-02-08  5:55 Stephen Rothwell
2017-05-31  4:33 Stephen Rothwell
2017-05-31  5:45 ` Heiner Kallweit
2017-05-31  7:19   ` Alexandre Belloni
2016-11-08  6:41 Stephen Rothwell
2016-11-08 22:21 ` Alexandre Belloni
2015-12-17  5:03 Stephen Rothwell
2015-12-17 11:21 ` Alexandre Belloni
2015-12-17 11:21   ` Alexandre Belloni
2015-12-18 15:30   ` Sasha Levin
2015-12-18 16:43     ` Alexandre Belloni
2015-12-22 19:27       ` Alexandre Belloni

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=20170411175220.43cd5280@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=hdegoede@redhat.com \
    --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.