From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Drake <drake@endlessm.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: linux-next <linux-next@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the input-current tree
Date: Tue, 18 Sep 2018 15:32:03 -0700 [thread overview]
Message-ID: <CAKdAkRR8NH8FxfRVsB2DCiyh7QVZLisqZgd1ZgHCnGpUO6KP-g@mail.gmail.com> (raw)
In-Reply-To: <20180919082500.74401754@canb.auug.org.au>
On Tue, Sep 18, 2018 at 3:25 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Dmitry,
>
> After merging the input-current tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "mem_sleep_current" [drivers/input/serio/i8042.ko] undefined!
>
> Caused by commit
>
> 1685830e59d4 ("Input: i8042 - enable keyboard wakeups by default when s2idle is used")
>
> I have used the version of input-current from next-20180918 for today.
Ugh, sorry, I dropped that patch from my tree for now.
Daniel, Rafael, I guess we can't make pm_suspend_via_s2idle() static
inline, but instead move it into kernel/power/suspend.c and make it
EXPORT_SYMBOL().
Thanks.
--
Dmitry
next prev parent reply other threads:[~2018-09-18 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 22:25 linux-next: build failure after merge of the input-current tree Stephen Rothwell
2018-09-18 22:32 ` Dmitry Torokhov [this message]
2018-09-20 8:02 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2019-05-23 22:24 Stephen Rothwell
2019-05-23 22:52 ` Dmitry Torokhov
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=CAKdAkRR8NH8FxfRVsB2DCiyh7QVZLisqZgd1ZgHCnGpUO6KP-g@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=drake@endlessm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--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).