From: Javier Martinez Canillas <javierm@redhat.com>
To: Doug Anderson <dianders@chromium.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>,
Robert Foss <robert.foss@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
jjsu@chromium.org, lschyi@chromium.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] drm/panel-edp: Allow querying the detected panel via sysfs
Date: Wed, 26 Jan 2022 09:25:26 +0100 [thread overview]
Message-ID: <6fdcfbcf-0546-6b4f-b50f-cf2382ad746f@redhat.com> (raw)
In-Reply-To: <CAD=FV=U8VGnRXv8MgofKzZF22_x0_X3M+AMfyPQ1u=yTXnFBQA@mail.gmail.com>
On 1/26/22 00:25, Doug Anderson wrote:
> On Tue, Jan 25, 2022 at 2:55 PM Javier Martinez Canillas
> <javierm@redhat.com> wrote:
[snip]
>> Should this new sysfs entry be documented in Documentation/ABI/ ?
>
> I'm not sure what the policy is here. I actually don't know that I'm
> too worried about this being an ABI. For the purposes of our tests
> then if something about this file changed (path changed or something
> like that) it wouldn't be a huge deal. Presumably the test itself
> would just "fail" in this case and that would clue us in that the ABI
> changed and we could adapt to whatever new way was needed to discover
> this.
>
> That being said, if the policy is that everything in sysfs is supposed
> to be ABI then I can add documentation for this...
>
I also don't know the policy, hence the question. But in any case, I
think that it could even be done as a follow-up if is needed.
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-01-26 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 21:54 Douglas Anderson
2022-01-25 22:55 ` Javier Martinez Canillas
2022-01-25 23:25 ` Doug Anderson
2022-01-26 8:25 ` Javier Martinez Canillas [this message]
2022-02-01 16:41 ` Doug Anderson
2022-02-01 17:02 ` Daniel Vetter
2022-02-01 17:22 ` Doug Anderson
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=6fdcfbcf-0546-6b4f-b50f-cf2382ad746f@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jjsu@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lschyi@chromium.org \
--cc=robert.foss@linaro.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®