From: Tony Lindgren <tony@atomide.com>
To: Ivan Jelincic <parazyd@dyne.org>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: omap2plus_defconfig: Update for dropped options.
Date: Thu, 4 Feb 2021 08:56:30 +0200 [thread overview]
Message-ID: <YBuankYwwMsG4MN9@atomide.com> (raw)
In-Reply-To: <20210203113426.18964-2-parazyd@dyne.org>
* Ivan Jelincic <parazyd@dyne.org> [210203 13:35]:
> Update omap2plus_defconfig for options that have been dropped:
>
> - SIMPLE_PM_BUS no longer selected.
Oh right, we now need to always select it. Will queue this for
fixes after the merge window. The other one I'll be queueing
for v5.13 as the merge window is about to open and I'll only
queue fixes for the next few weeks :)
Regards,
Tony
next prev parent reply other threads:[~2021-02-04 6:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 11:34 [PATCH 1/2] ARM: omap2plus_defconfig: Enable Netfilter components as modules Ivan Jelincic
2021-02-03 11:34 ` [PATCH 2/2] ARM: omap2plus_defconfig: Update for dropped options Ivan Jelincic
2021-02-04 6:56 ` Tony Lindgren [this message]
2021-02-05 13:15 ` Grygorii Strashko
2021-02-05 13:17 ` Ivan J.
2021-02-05 13:30 ` Tony Lindgren
2021-02-05 14:25 ` Grygorii Strashko
2021-02-05 14:46 ` Tony Lindgren
2021-02-05 15:04 ` Grygorii Strashko
2021-02-05 15:04 ` Grygorii Strashko
2021-02-06 7:23 ` Tony Lindgren
2021-02-05 13:18 ` [PATCH 1/2] ARM: omap2plus_defconfig: Enable Netfilter components as modules Grygorii Strashko
2021-02-05 13:33 ` Tony Lindgren
2021-02-05 14:01 ` Grygorii Strashko
-- strict thread matches above, loose matches on Subject: below --
2021-01-26 12:21 [PATCH 1/2] ARM: omap2plus_defconfig: Update for moved options Tony Lindgren
2021-01-26 12:21 ` [PATCH 2/2] ARM: omap2plus_defconfig: Update for dropped options Tony Lindgren
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=YBuankYwwMsG4MN9@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=parazyd@dyne.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;
as well as URLs for NNTP newsgroup(s).