[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4e993ce-4630-6d89-077b-e2f18fadef02@osg.samsung.com>
Date: Thu, 16 Mar 2017 11:07:23 -0300
From: Javier Martinez Canillas <javier@....samsung.com>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-i2c@...r.kernel.org
Subject: Re: [PATCH 4/4] eeprom: at24: Add OF device ID table
Hello Wolfram,
On 03/16/2017 10:36 AM, Wolfram Sang wrote:
>
>> Sorry, for not explaining myself correctly. I meant to ask who can do what you
>> suggested before. I'm certainly not familiar with this driver to identify what
>> is the minimum set of compatible strings that can be used as generic fallback.
>
> Well, I am the maintainer of this driver :) But we should definately get
Oh right, silly me :)
> 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? To be honest I think I'll just give
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.
I've posted patches for all the drivers that could be affected when reporting a
proper OF modalias by the core and also the RFC patch to properly report it [0].
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.
[0]: https://lkml.org/lkml/2015/7/30/494
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
Powered by blists - more mailing lists