linux-kernel - Re: [PATCH] extcon: arizona: Update naming for second jack detection DT binding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAL_JsqKN0fj97Zxw=xQx9kioA-cHomWRQ=8ohXNk_+1WGz+Zaw@mail.gmail.com>
Date:	Fri, 20 Nov 2015 10:00:55 -0600
From:	Rob Herring <robh@...nel.org>
To:	Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>,
	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	Chanwoo Choi <cw00.choi@...sung.com>, myungjoo.ham@...sung.com,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH] extcon: arizona: Update naming for second jack detection
 DT binding

On Fri, Nov 20, 2015 at 8:55 AM, Richard Fitzgerald
<rf@...nsource.wolfsonmicro.com> wrote:
> On Fri, 2015-11-20 at 08:39 -0600, Rob Herring wrote:
>> On Fri, Nov 20, 2015 at 08:53:59AM +0000, Charles Keepax wrote:
>> > Update the name for the second jack detection pin binding to be a little
>> > less confusing.
>>
>> This breaks compatibility with old dtbs. Either the driver needs to
>> support both names or you just have to live with the old name.
>>
>
> This is a new DT option, it's never gone into a release kernel so there
> can't be any dtbs using it.

I see the thread now. The commit message should make that clear.

Acked-by: Rob Herring <robh@...nel.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/