From: Peter Rosin <peda@axentia.se>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
Peter Korsgaard <peter.korsgaard@barco.com>,
Michael Hennerich <michael.hennerich@analog.com>,
Michael Shych <michaelsh@mellanox.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] i2c: mux: rename files to not have superfluous prefixes
Date: Sat, 12 Aug 2017 23:03:56 +0200 [thread overview]
Message-ID: <cf6096a6-c25f-86dc-d474-19accedabd36@axentia.se> (raw)
In-Reply-To: <20170812142625.xugkg2swbuazchug@ninjato>
On 2017-08-12 16:26, Wolfram Sang wrote:
> Hi peda,
>
>> In the light of the rant from Linus the other week [1], I thought this
>> might be a good idea?
>
> I am still not decided on this one. I tried to do it with the core files
> and didn't find a convincing solution there. Also, the churn is quite
> high: git history becomes less usable, likely broken references, it is
> not consistent in the kernel anyhow...
>
> So, I decided to work on real issues for now. The pain point for me is
> not reached yet. But if it is for you (or someone else), I am open to
> look at an subsystem wide solution.
Yeah, there are a few downsides and I agree that the whole i2c subsystem
should be "converted" at the same time, probably directly after some
future rc1. Feel free to use this patch (or an adjusted version) if/when
the time comes, or poke me and I'll redo it.
In other words, I'm not super-committed to this patch, and will just drop
it for now...
Cheers,
Peter
prev parent reply other threads:[~2017-08-12 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 9:07 [PATCH] i2c: mux: rename files to not have superfluous prefixes Peter Rosin
2017-08-06 9:37 ` Michael Shych
2017-08-12 14:26 ` Wolfram Sang
2017-08-12 21:03 ` Peter Rosin [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=cf6096a6-c25f-86dc-d474-19accedabd36@axentia.se \
--to=peda@axentia.se \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michael.hennerich@analog.com \
--cc=michaelsh@mellanox.com \
--cc=peter.korsgaard@barco.com \
--cc=wsa@the-dreams.de \
/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