From: Marek Behun <kabel@blackhole.sk>
To: Dan Murphy <dmurphy@ti.com>
Cc: <ultracoolguy@tutanota.com>, Pavel <pavel@ucw.cz>,
Linux Leds <linux-leds@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH] leds: lm3697: Fix out-of-bound access
Date: Tue, 6 Oct 2020 17:14:19 +0200 [thread overview]
Message-ID: <20201006171419.5f5d9df4@blackhole.sk> (raw)
In-Reply-To: <85515ccd-3431-4565-eaad-3e1d116bf89f@ti.com>
On Tue, 6 Oct 2020 09:57:08 -0500
Dan Murphy <dmurphy@ti.com> wrote:
> Unfortunately we cannot and should not change the ABI now.
>
> Using the led-sources as the bank indicator does not conform to the
> definition of the description of the led-sources in the yaml.
>
> The preference was to use the led-sources to define the LED out to the bank.
>
> Here is the conversation on how the driver got to where it is.
>
> https://lore.kernel.org/patchwork/patch/972337/
>
> Dan
>
Oh, if this was discussed already, then never mind. Sorry for taking
your time.
Marek
next prev parent reply other threads:[~2020-10-06 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201005141334.36d9441a@blackhole.sk>
[not found] ` <MIt2NiS--3-2@tutanota.com>
[not found] ` <3c5fce56-8604-a7d5-1017-8a075f67061e@ti.com>
[not found] ` <MItBqjy--3-2@tutanota.com>
[not found] ` <966c3f39-1310-dd60-6f33-0d9464ed2ff1@ti.com>
[not found] ` <MItOR9Z--3-2@tutanota.com>
[not found] ` <20201005164808.slrtmsvmw4pvwppm@falbala.internal.home.lespocky.de>
[not found] ` <MItjEho--3-2@tutanota.com>
[not found] ` <20201005173227.GA6431@duo.ucw.cz>
[not found] ` <20201006093356.6d25b280@blackhole.sk>
[not found] ` <MIxm3uX--3-2@tutanota.com>
[not found] ` <144aa75a-4369-cd81-d7dc-2354a9afd7c5@ti.com>
2020-10-06 14:41 ` [PATCH] leds: lm3697: Fix out-of-bound access Marek Behun
2020-10-06 14:57 ` Dan Murphy
2020-10-06 15:14 ` Marek Behun [this message]
2020-10-06 17:26 ` Pavel Machek
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=20201006171419.5f5d9df4@blackhole.sk \
--to=kabel@blackhole.sk \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=ultracoolguy@tutanota.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;
as well as URLs for NNTP newsgroup(s).