From: Daniel Vetter <daniel@ffwll.ch>
To: Kees Cook <keescook@chromium.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: shorten debugfs output simple attributes
Date: Tue, 16 Apr 2013 09:33:07 +0200 [thread overview]
Message-ID: <20130416073307.GD27612@phenom.ffwll.local> (raw)
In-Reply-To: <CAGXu5jL4JMFTWKpo4bK7SGOSoMYYM8O0c4etqzsMdgRwwQkJ-A@mail.gmail.com>
On Fri, Apr 12, 2013 at 11:00:20AM -0700, Kees Cook wrote:
> On Fri, Apr 12, 2013 at 2:10 AM, Mika Kuoppala
> <mika.kuoppala@linux.intel.com> wrote:
> > commit 647416f9eefe7699754b01b9fc82758fde83248c
> > Author: Kees Cook <keescook@chromium.org>
> > Date: Sun Mar 10 14:10:06 2013 -0700
> >
> > drm/i915: use simple attribute in debugfs routines
> >
> > made i915_next_seqno debugfs entry to crop it's output
> > if returned value was large enough. Using simple_attr
> > will limit the output to 24 bytes.
> >
> > Fix is to strip out preamples on all simple attributes
> > that have one.
> >
> > v2: Fix all simple attributes (Daniel Vetter)
> >
> > Cc: Kees Cook <keescook@chromium.org>
> > Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> Acked-by: Kees Cook <keescook@chromium.org>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-04-16 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 13:22 [PATCH 1/1] drm/i915: shorten i915_next_seqno debugfs output Mika Kuoppala
2013-04-11 16:02 ` Kees Cook
2013-04-11 16:15 ` Mika Kuoppala
2013-04-11 16:42 ` Kees Cook
2013-04-12 9:15 ` Mika Kuoppala
2013-04-12 17:57 ` Kees Cook
2013-04-12 9:10 ` [PATCH] drm/i915: shorten debugfs output simple attributes Mika Kuoppala
2013-04-12 18:00 ` Kees Cook
2013-04-16 7:33 ` Daniel Vetter [this message]
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=20130416073307.GD27612@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keescook@chromium.org \
/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