From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Sebastian Reichel <sre@kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Timon Baetz <timon.baetz@protonmail.com>
Subject: Re: mmotm 2021-01-04-16-56 uploaded (drivers/power/supply/max8997_charger.c)
Date: Mon, 4 Jan 2021 20:26:04 -0800 [thread overview]
Message-ID: <6ed164be-e80e-e69f-c164-4e1c68465728@infradead.org> (raw)
In-Reply-To: <20210105005703.XhY3BDF8Y%akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]
On 1/4/21 4:57 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2021-01-04-16-56 has been uploaded to
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> https://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
>
> This tree is partially included in linux-next. To see which patches are
> included in linux-next, consult the `series' file. Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
Hi,
Commit bb118e5178b3 in linux-next seems to introduce a few build problems:
ld: drivers/power/supply/max8997_charger.o: in function `max8997_battery_extcon_evt_worker':
max8997_charger.c:(.text+0xa3): undefined reference to `extcon_get_state'
ld: max8997_charger.c:(.text+0x102): undefined reference to `extcon_get_state'
ld: max8997_charger.c:(.text+0x161): undefined reference to `extcon_get_state'
ld: max8997_charger.c:(.text+0x1c0): undefined reference to `extcon_get_state'
ld: max8997_charger.c:(.text+0x21f): undefined reference to `extcon_get_state'
ld: drivers/power/supply/max8997_charger.o: in function `max8997_battery_probe':
max8997_charger.c:(.text+0x962): undefined reference to `extcon_get_edev_by_phandle'
ld: max8997_charger.c:(.text+0xab0): undefined reference to `devm_extcon_register_notifier_all'
CONFIG_EXTCON=m
CONFIG_CHARGER_MAX8997=y
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r7006.gz --]
[-- Type: application/gzip, Size: 28142 bytes --]
next prev parent reply other threads:[~2021-01-05 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 0:57 mmotm 2021-01-04-16-56 uploaded akpm
2021-01-05 4:26 ` Randy Dunlap [this message]
2021-01-05 14:04 ` mmotm 2021-01-04-16-56 uploaded (drivers/power/supply/max8997_charger.c) Sebastian Reichel
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=6ed164be-e80e-e69f-c164-4e1c68465728@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sfr@canb.auug.org.au \
--cc=sre@kernel.org \
--cc=timon.baetz@protonmail.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).