From: Heiner Kallweit <hkallweit1@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Lowe <dave-lowe@ntlworld.com>
Subject: Re: linux-next: build failure after merge of the rtc tree
Date: Wed, 31 May 2017 07:45:07 +0200 [thread overview]
Message-ID: <56de728c-b7eb-8093-e39e-41cf9b743d16@gmail.com> (raw)
In-Reply-To: <20170531143349.561d5e77@canb.auug.org.au>
Am 31.05.2017 um 06:33 schrieb Stephen Rothwell:
> Hi Alexandre,
>
> After merging the rtc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/rtc/rtc-ds1307.c: In function 'ds1307_probe':
> drivers/rtc/rtc-ds1307.c:1410:29: error: 'struct ds1307' has no member named 'client'
> if (chip->alarm && (ds1307->client->irq > 0 ||
> ^
ds1307->client->irq would have to be replaced with ds1307->irq.
Same what the regmap patch does e.g. at line 1477.
The regmap patch removes member client from struct ds1307.
Rgds, Heiner
>
> Caused by commit
>
> 345b89453dda ("rtc: rtc-ds1307: enable support for mcp794xx as a wakeup source without IRQ")
>
> interacting with commit
>
> 11e5890b5342 ("rtc: ds1307: convert driver to regmap")
>
> I have used the rtc tree from next-20170530 for today.
>
next prev parent reply other threads:[~2017-05-31 5:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 4:33 linux-next: build failure after merge of the rtc tree Stephen Rothwell
2017-05-31 5:45 ` Heiner Kallweit [this message]
2017-05-31 7:19 ` Alexandre Belloni
-- 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-04-10 6:04 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
2017-04-14 10:09 ` Alexandre Belloni
2017-04-14 16:33 ` Stephen Rothwell
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=56de728c-b7eb-8093-e39e-41cf9b743d16@gmail.com \
--to=hkallweit1@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=dave-lowe@ntlworld.com \
--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 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.