public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Jean Delvare <jdelvare@suse.de>,
	Linux I2C <linux-i2c@vger.kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] i2c: Drop legacy muxing pseudo-drivers
Date: Wed, 27 Sep 2023 08:20:55 +0200	[thread overview]
Message-ID: <ZRPJx5OFGaAkXJzg@ninjato> (raw)
In-Reply-To: <20230926212720.adcn42akrnj72oxl@zenone.zhora.eu>

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]


> I'm somewhat conflicted, on one hand I like the cleanup. But on
> the other I think that they don't do any harm if they stay where
> they are. There are lots of drivers that look outdated and need
> maintenance, we can't just remove them... right?

I'd agree if they are proper drivers. If they are hacks which would be
solved entirely differently today, I am all for removing the bad
examples from the tree. I happily take Jean's offer to rewrite the
drivers with proper mux-interfaces, if any complain should arise. I
wouldn't wait for it, though ;)


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-09-27  6:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 11:37 [PATCH] i2c: Drop legacy muxing pseudo-drivers Jean Delvare
2023-09-26 16:33 ` Nick Desaulniers
2023-09-26 21:27 ` Andi Shyti
2023-09-27  6:20   ` Wolfram Sang [this message]
2023-09-27  8:24   ` Jean Delvare
2023-09-27 19:44 ` Wolfram Sang
2023-09-27 20:21   ` Jean Delvare

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=ZRPJx5OFGaAkXJzg@ninjato \
    --to=wsa@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=ndesaulniers@google.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