From: Finn Thain <fthain@linux-m68k.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Arnd Bergmann <arnd@arndb.de>, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] macintosh: fix via-pmu and via-cuda build errors
Date: Thu, 7 Apr 2022 17:41:20 +1000 (AEST) [thread overview]
Message-ID: <2187e41c-aecf-ff8c-9e53-d5f0c3f2283f@linux-m68k.org> (raw)
In-Reply-To: <e0d0b771-2459-1050-03f8-1bd1f70d7569@csgroup.eu>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On Thu, 7 Apr 2022, Christophe Leroy wrote:
> Le 07/04/2022 à 05:16, Randy Dunlap a écrit :
> >
> >
> > On 4/6/22 19:37, Randy Dunlap wrote:
> >> When CONFIG_INPUT=m, the input_*() family of functions is not
> >> available to builtin drivers.
> >>
> >> When CONFIG_RTC_CLASS is not set, rtc_tm_to_time64() is not defined.
> >>
> >> Fix multiple build errors by making these Kconfig symbols required by
> >> ADB_CUDA (RTC_CLASS) and ADB_PMU (RTC_CLASS and INPUT).
> >
> > Ah yes, Finn has already fixed the INPUT problems here.
>
> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/d987663bbed18d7dbf106db6066a759040b4e57a.1647837028.git.fthain@linux-m68k.org/
>
> >
> > Maybe that patch hasn't been merged anywhere yet?
>
> The patch has comments, I guess we are waiting for a new version ?
>
I'll send a new version, though I expect it will attract comments too.
next prev parent reply other threads:[~2022-04-07 7:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 2:37 Randy Dunlap
2022-04-07 3:16 ` Randy Dunlap
2022-04-07 7:14 ` Christophe Leroy
2022-04-07 7:41 ` Finn Thain [this message]
2022-04-07 7:22 ` Christophe Leroy
2022-04-07 7:31 ` Finn Thain
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=2187e41c-aecf-ff8c-9e53-d5f0c3f2283f@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=geert@linux-m68k.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®