From: Sean Paul <sean@poorly.run>
To: Pekka Paalanen <ppaalanen@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
Sean Paul <seanpaul@chromium.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Sean Paul <sean@poorly.run>
Subject: Re: [PATCH] drm: Funnel drm logs to tracepoints
Date: Tue, 3 Dec 2019 14:10:54 -0500 [thread overview]
Message-ID: <20191203191054.GA162979@art_vandelay> (raw)
In-Reply-To: <20191017102216.20f98533@eldfell.localdomain>
On Thu, Oct 17, 2019 at 10:22:16AM +0300, Pekka Paalanen wrote:
> On Wed, 16 Oct 2019 15:23:45 +0200
> Thomas Zimmermann <tzimmermann@suse.de> wrote:
>
> > Hi
> >
> > Am 16.10.19 um 15:05 schrieb Pekka Paalanen:
>
> > > specifically be available in production. So a new file in some fs
> > > somewhere it should be, and userspace in production can read it at will
> > > to attach to a bug report.
> > >
> > > Those semantics, "only use this content for attaching into a bug
> > > report" should be made very clear in the UAPI.
> >
> > Has this ever worked? As soon as a userspace program starts depending on
> > the content of this file, it becomes kabi. From the incidents I know,
> > Linus has always been quite strict about this. Even for broken interfaces.
>
> The kernel log content is not kabi, is it? I've seen it change plenty
> during the years. This would be just another similar log with free-form
> text.
>
Ok, so given the more structured version of this set [1] was not well received,
are we all comfortable going with the freeform approach in this version?
Sean
[1]- https://lists.freedesktop.org/archives/dri-devel/2019-November/243230.html
>
> Thanks,
> pq
--
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-12-03 19:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 20:48 [PATCH] drm: Funnel drm logs to tracepoints Sean Paul
2019-10-14 8:52 ` Daniel Vetter
2019-10-15 11:18 ` Joonas Lahtinen
2019-10-15 12:07 ` Thomas Zimmermann
2019-10-15 16:18 ` Rob Clark
2019-10-15 19:11 ` Sean Paul
2019-10-15 20:02 ` Ville Syrjälä
2019-10-15 22:35 ` Daniel Vetter
2019-10-16 13:05 ` Pekka Paalanen
2019-10-16 13:23 ` Thomas Zimmermann
2019-10-16 15:55 ` Sean Paul
2019-10-17 7:22 ` Pekka Paalanen
2019-12-03 19:10 ` Sean Paul [this message]
2019-12-03 21:20 ` Daniel Vetter
2019-12-04 7:33 ` Pekka Paalanen
2019-12-04 9:14 ` Daniel Vetter
2019-12-04 9:54 ` Pekka Paalanen
2019-12-04 13:02 ` Daniel Vetter
2019-12-04 13:52 ` Sean Paul
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=20191203191054.GA162979@art_vandelay \
--to=sean@poorly.run \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ppaalanen@gmail.com \
--cc=seanpaul@chromium.org \
--cc=tzimmermann@suse.de \
/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