From: Hans de Goede <hdegoede@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Subject: Re: linux-next: Tree for Nov 2 (drivers/platform/x86/amd-pmc.o)
Date: Tue, 2 Nov 2021 16:26:13 +0100 [thread overview]
Message-ID: <0bd6303e-1f93-1fc0-1dcc-329092ac9963@redhat.com> (raw)
In-Reply-To: <caa259b7-0560-647d-80d0-6dd25a6f09d2@infradead.org>
Hi,
On 11/2/21 16:14, Randy Dunlap wrote:
> On 11/2/21 1:15 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v5.17 related material to your linux-next included
>> trees until the merge window has closed.
>>
>> Changes since 20211101:
>>
>
>
> on i386:
>
> ld: drivers/platform/x86/amd-pmc.o: in function `amd_pmc_suspend':
> amd-pmc.c:(.text+0x5db): undefined reference to `rtc_class_open'
> ld: amd-pmc.c:(.text+0x5ea): undefined reference to `rtc_read_alarm'
> ld: amd-pmc.c:(.text+0x604): undefined reference to `rtc_read_time'
> ld: amd-pmc.c:(.text+0x660): undefined reference to `rtc_alarm_irq_enable'
>
>
> Also "depends on RTC_CLASS" ?
Yes, thank you for reporting this. I've just send out my main PR
to Linus for 5.16, which includes the amd-pmc changes here.
I'll prepare a patch and include that in my first fixes PR to Linus
once 5.16-rc1 is out.
Regards,
Hans
prev parent reply other threads:[~2021-11-02 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 8:15 linux-next: Tree for Nov 2 Stephen Rothwell
2021-11-02 15:14 ` linux-next: Tree for Nov 2 (drivers/platform/x86/amd-pmc.o) Randy Dunlap
2021-11-02 15:26 ` Hans de Goede [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=0bd6303e-1f93-1fc0-1dcc-329092ac9963@redhat.com \
--to=hdegoede@redhat.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).