From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Randy Dunlap <rdunlap@infradead.org>, Pavel Machek <pavel@ucw.cz>,
Sekhar Nori <nsekhar@ti.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH 0/2] More (hopefully final) Kconfig clean-up after IDE removal
Date: Wed, 4 Aug 2021 14:34:24 +0200 [thread overview]
Message-ID: <20210804123426.16947-1-lukas.bulwahn@gmail.com> (raw)
Dear Christoph, dear Jens,
here is a follow-up to the issue of Kconfig references to obsolete IDE configs,
which I first identified and addressed in commit 094121ef815f ("arch: Kconfig:
clean up obsolete use of HAVE_IDE").
Following checkkconfigsymbols.py indications, this patch series cleans up all
references to removed IDE Kconfig symbol throughout the current kernel tree.
Pavel, Sekhar, Bartosz, you are CCed, just to let know about minor follow-up
cleanup in your files.
Christoph, please review and ack.
Jens, please pick these two further clean-up patches.
Best regards,
Lukas
Lukas Bulwahn (2):
leds: trigger: remove reference to obsolete CONFIG_IDE_GD_ATA
arm: davinci: remove reference to obsolete BLK_DEV_PALMCHIP_BK3710
arch/arm/mach-davinci/board-dm644x-evm.c | 3 +--
arch/arm/mach-davinci/board-dm646x-evm.c | 3 +--
arch/arm/mach-davinci/board-neuros-osd2.c | 3 +--
drivers/leds/trigger/Kconfig | 2 +-
4 files changed, 4 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2021-08-04 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 12:34 Lukas Bulwahn [this message]
2021-08-04 12:34 ` [PATCH 1/2] leds: trigger: remove reference to obsolete CONFIG_IDE_GD_ATA Lukas Bulwahn
2021-08-18 7:00 ` Pavel Machek
2021-08-04 12:34 ` [PATCH 2/2] arm: davinci: remove reference to obsolete BLK_DEV_PALMCHIP_BK3710 Lukas Bulwahn
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=20210804123426.16947-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=axboe@kernel.dk \
--cc=bgolaszewski@baylibre.com \
--cc=hch@lst.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.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).