From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Joel Stanley <joel@jms.id.au>,
Florian Fainelli <f.fainelli@gmail.com>,
Thierry Reding <treding@nvidia.com>,
Dmitry Osipenko <digetx@gmail.com>,
Mark Brown <broonie@kernel.org>,
William Zhang <william.zhang@broadcom.com>,
Stephan Gerhold <stephan@gerhold.net>,
Michael Walle <michael@walle.cc>,
Sudeep Holla <sudeep.holla@arm.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Adam Ford <aford173@gmail.com>,
Merlijn Wajer <merlijn@wizzup.org>,
Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 04/11] ARM: defconfig: drop CONFIG_SERIAL_OMAP references
Date: Mon, 22 Aug 2022 08:46:12 +0300 [thread overview]
Message-ID: <YwMYJD3ohx2UNMXG@atomide.com> (raw)
In-Reply-To: <20220818135737.3143895-3-arnd@kernel.org>
* Arnd Bergmann <arnd@kernel.org> [220818 13:51]:
> From: Arnd Bergmann <arnd@arndb.de>
>
> This driver is mutually exclusive with the new 8250_OMAP
> driver, so 'make defconfig' turns it off already. Drop
> the reference now.
Acked-by: Tony Lindgren <tony@atomide.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-22 5:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220818135522.3143514-1-arnd@kernel.org>
2022-08-18 13:57 ` [PATCH 02/11] ARM: defconfig: clean up multi_v4t and multi_v5 configs Arnd Bergmann
2022-08-18 13:57 ` [PATCH 03/11] ARM: defconfig: drop CONFIG_NET_VENDOR_ASIX=y Arnd Bergmann
2022-08-18 13:57 ` [PATCH 04/11] ARM: defconfig: drop CONFIG_SERIAL_OMAP references Arnd Bergmann
2022-08-22 5:46 ` Tony Lindgren [this message]
2022-08-18 13:57 ` [PATCH 05/11] ARM: defconfig: drop CONFIG_DRM_RCAR_LVDS Arnd Bergmann
2022-08-18 13:57 ` [PATCH 06/11] ARM: defconfig: drop CONFIG_PTP_1588_CLOCK=y Arnd Bergmann
2022-08-18 15:10 ` Richard Cochran
2022-08-18 13:57 ` [PATCH 07/11] ARM: defconfig: drop CONFIG_SND_SOC_FSL_SAI Arnd Bergmann
2022-08-18 13:57 ` [PATCH 08/11] ARM: defconfig: drop CONFIG_USB_FSL_USB2 Arnd Bergmann
2022-08-18 14:09 ` Greg Kroah-Hartman
2022-08-18 13:57 ` [PATCH 09/11] ARM: defconfig: drop CONFIG_MICROCHIP_PIT64B Arnd Bergmann
2022-08-19 7:31 ` Claudiu.Beznea
2022-08-18 13:57 ` [PATCH 10/11] ARM: defconfig: fix CONFIG_SND_SOC_AC97_CODEC name Arnd Bergmann
2022-08-18 13:57 ` [PATCH 11/11] musb: fix USB_MUSB_TUSB6010 dependency Arnd Bergmann
2022-08-18 14:08 ` Greg Kroah-Hartman
2022-08-18 14:27 ` Arnd Bergmann
2022-08-18 14:33 ` Greg Kroah-Hartman
2022-08-25 13:40 ` [PATCH 02/11] ARM: defconfig: clean up multi_v4t and multi_v5 configs Linus Walleij
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=YwMYJD3ohx2UNMXG@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=digetx@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=merlijn@wizzup.org \
--cc=michael@walle.cc \
--cc=stephan@gerhold.net \
--cc=sudeep.holla@arm.com \
--cc=treding@nvidia.com \
--cc=william.zhang@broadcom.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).