From: Arnd Bergmann <arnd@arndb.de>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "yuehaibing@huawei.com" <yuehaibing@huawei.com>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>
Subject: Re: [PATCH] rtc: bd70528: fix link error
Date: Thu, 8 Aug 2019 22:40:49 +0200 [thread overview]
Message-ID: <CAK8P3a1hJBF40n49furd2pJ3tPCKNfELXweNyab+CZZo1fvZTg@mail.gmail.com> (raw)
In-Reply-To: <f22cf88f836159b9f5428c6297d8e54b4639e1db.camel@fi.rohmeurope.com>
On Thu, Aug 8, 2019 at 9:53 PM Vaittinen, Matti
<Matti.Vaittinen@fi.rohmeurope.com> wrote:
> On Thu, 2019-08-08 at 10:29 +0800, Yuehaibing wrote:
> > On 2019/7/9 13:25, Vaittinen, Matti wrote:
> > > awkward at first sight but indeed - depends on BD70528_WATCHDOG
> > > disallows BD70528_WATCHDOG=m with RTC_DRV_BD70528=y while
> > > !BD70528_WATCHDOG allows BD70528_WATCHDOG=n. Brilliant and exactly
> > > what
> > > we need :) Thanks a bunch!
> >
> > Hello Vaittinen,
> >
> > the issue still exists in linux-next 20190807, any plan?
> >
>
> Sorry folks. I thought Arnd would send new patch - I didn't want to
> steal his work ;) I will be back to my normal life next week so I
> will send a patch at monday if the issue is still open!
Sorry I lost track, and thanks for the offer to take care of it.
Please add my one
Reported-by: Arnd Bergmann <arnd@arndb.de>
and/or
Suggested-by: Arnd Bergmann <arnd@arndb.de>
as appropriate when you create that patch.
Arnd
prev parent reply other threads:[~2019-08-08 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 12:41 [PATCH] rtc: bd70528: fix link error Arnd Bergmann
2019-07-08 13:24 ` Vaittinen, Matti
2019-07-08 16:10 ` Arnd Bergmann
2019-07-09 5:25 ` Vaittinen, Matti
2019-08-08 2:29 ` Yuehaibing
2019-08-08 19:53 ` Vaittinen, Matti
2019-08-08 20:40 ` Arnd Bergmann [this message]
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=CAK8P3a1hJBF40n49furd2pJ3tPCKNfELXweNyab+CZZo1fvZTg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=yuehaibing@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).