public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH 4/4] eeprom: at24: Add OF device ID table
Date: Thu, 16 Mar 2017 16:05:49 +0100	[thread overview]
Message-ID: <20170316150549.GA3988@katana> (raw)
In-Reply-To: <b4e993ce-4630-6d89-077b-e2f18fadef02@osg.samsung.com>

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


> > Rob into the boat if he is OK with updating all DTS files having such an
> > EEPROM.
> >
> 
> Agreed, are you going to take care of that?

Nope, sorry, no bandwidth. You might ask Lee, he was very interested in
getting proper I2C OF support upstream.

> up on this task, it has been a big time sink and I had to explain over and over
> to different people what the problem is with the I2C modalias uevent reporting.

Next time, maybe do a wiki page and point people to it? That being said,
we should probably create a wiki page on the I2C wiki anyhow.
Documenting the current state of affairs. That I would do when I finally
get around to brush up I2C wiki.

> But it seems that for many maintainers this is just an unnecessary churn and they
> don't think there's an issue with the current behaviour. So it feels I'm causing
> more harm than good by keep pushing this.

I understand somehow. They probably were reluctant to change something
that is working, even if it is not pretty. I'm not saying it's not worth
it, yet one needs energy and motivation to push it through.


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

  reply	other threads:[~2017-03-16 15:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 15:16 [PATCH 0/4] misc: Add OF device table to I2C drivers that are missing it Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 1/4] misc: tsl2550: Add OF device ID table Javier Martinez Canillas
2017-03-14 20:53   ` Arnd Bergmann
2017-03-14 15:16 ` [PATCH 2/4] misc: ds1682: " Javier Martinez Canillas
2017-03-14 20:46   ` Arnd Bergmann
2017-03-15  0:38     ` Javier Martinez Canillas
2017-03-15  3:26       ` Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 3/4] eeprom: idt_89hpesx: " Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 4/4] eeprom: at24: " Javier Martinez Canillas
2017-03-14 22:59   ` Andy Shevchenko
2017-03-15  0:15     ` Javier Martinez Canillas
2017-03-15  7:58       ` Wolfram Sang
2017-03-15 10:58         ` Javier Martinez Canillas
2017-03-15 11:21           ` Andy Shevchenko
2017-03-15 11:39             ` Javier Martinez Canillas
2017-03-15 22:43               ` Andy Shevchenko
2017-03-16 12:28                 ` Javier Martinez Canillas
2017-03-16 13:07           ` Wolfram Sang
2017-03-16 13:13             ` Javier Martinez Canillas
2017-03-16 13:36               ` Wolfram Sang
2017-03-16 14:07                 ` Javier Martinez Canillas
2017-03-16 15:05                   ` Wolfram Sang [this message]
2017-03-16 15:39                     ` Javier Martinez Canillas
2017-03-20 16:45                       ` Javier Martinez Canillas

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=20170316150549.GA3988@katana \
    --to=wsa@the-dreams.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=javier@osg.samsung.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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