From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Thierry Reding <thierry.reding@gmail.com>,
kernel <kernel@savoirfairelinux.com>,
Sascha Hauer <kernel@pengutronix.de>,
Jerome Oufella <jerome.oufella@savoirfairelinux.com>,
Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] bus: ts-nbus: remove bus driver without user
Date: Wed, 11 Dec 2019 08:11:07 +0100 [thread overview]
Message-ID: <20191211071107.ogyuxnwphlw5txe3@pengutronix.de> (raw)
In-Reply-To: <CACRpkdb5L9S1McY41FUivZD7DUPOtbvTPVgVOvcVWr114GuzPw@mail.gmail.com>
Hello Linus,
On Wed, Dec 11, 2019 at 12:08:14AM +0100, Linus Walleij wrote:
> On Tue, Dec 10, 2019 at 10:28 PM Uwe Kleine-König
> <u.kleine-koenig@pengutronix.de> wrote:
> > On Tue, Dec 10, 2019 at 10:19:55PM +0100, Linus Walleij wrote:
>
> > > So I would rather ask: who is hurt by it being around?
> >
> > It's one of the legacy PWM API users, and when I worked at improving
> > it Thierry wondered if it's worth keeping the driver given it has no
> > users[1].
> >
> > I don't care much either way, but if we keep the driver "looks dead"
> > shouldn't be an excuse to not take cleanup patches.
>
> Hm are cleanup patches not getting applied?
> Isn't the real problem (my halfguess) that drivers/bus/* is a bit
> orphaned?
>
> Whenever I want to change something there I just send the patches
> to the [ARM] SoC maintainers and ask them to apply it.
> arm@kernel.org soc@kernel.org
>
> If it means that you'd have to do tons of cleanups for nonexisting
> or ungrateful users I'd say send a patch to delete it.
OK, I will readd that driver to my (already long) todo list and send
patches to them when I come around to work in that area again.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-12-11 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 19:45 [PATCH] bus: ts-nbus: remove bus driver without user Uwe Kleine-König
2019-01-11 12:52 ` Linus Walleij
2019-01-11 15:04 ` Uwe Kleine-König
2019-01-11 19:56 ` Linus Walleij
2019-12-10 17:15 ` Uwe Kleine-König
2019-12-10 21:19 ` Linus Walleij
2019-12-10 21:27 ` Uwe Kleine-König
2019-12-10 23:08 ` Linus Walleij
2019-12-11 7:11 ` Uwe Kleine-König [this message]
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=20191211071107.ogyuxnwphlw5txe3@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=arnd@arndb.de \
--cc=jerome.oufella@savoirfairelinux.com \
--cc=kernel@pengutronix.de \
--cc=kernel@savoirfairelinux.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastien.bourdelin@savoirfairelinux.com \
--cc=thierry.reding@gmail.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).