From: Rob Herring <robh@kernel.org>
To: Sean Paul <sean@poorly.run>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
freedreno <freedreno@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v2] drm: Convert to using %pOFn instead of device_node.name
Date: Tue, 6 Nov 2018 15:57:16 -0600 [thread overview]
Message-ID: <CAL_JsqJaoXd5xhhi1kvLHrRiMh1BTbnQ=p8Oz9893uVMJ1UpEQ@mail.gmail.com> (raw)
In-Reply-To: <20181001081659.GW11082@phenom.ffwll.local>
On Mon, Oct 1, 2018 at 3:17 AM Daniel Vetter <daniel@ffwll.ch> wrote:
>
> On Fri, Sep 28, 2018 at 05:50:44PM -0500, Rob Herring wrote:
> > In preparation to remove the node name pointer from struct device_node,
> > convert printf users to use the %pOFn format specifier.
> >
> > For drm_modes.c, the full node path is already printed out, so printing
> > just the node name a 2nd time is redundant and can be removed.
> >
> > Cc: Gustavo Padovan <gustavo@padovan.org>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Sean Paul <sean@poorly.run>
> > Cc: David Airlie <airlied@linux.ie>
> > Acked-by: Rob Clark <robdclark@gmail.com>
> > Cc: dri-devel@lists.freedesktop.org
> > Cc: linux-arm-msm@vger.kernel.org
> > Cc: freedreno@lists.freedesktop.org
> > Signed-off-by: Rob Herring <robh@kernel.org>
> > ---
> > v2:
> > - Add to commit msg that we're dropping redundant printing of node name.
>
> Applied, thanks for the patch.
It appears this hasn't been.
> Aside, still don't want drm-misc commit rights so you can offload these
> yourself?
No thanks.
Rob
next prev parent reply other threads:[~2018-11-06 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 22:50 [PATCH v2] drm: Convert to using %pOFn instead of device_node.name Rob Herring
2018-10-01 8:16 ` Daniel Vetter
2018-11-06 21:57 ` Rob Herring [this message]
2018-11-06 22:26 ` Daniel Vetter
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='CAL_JsqJaoXd5xhhi1kvLHrRiMh1BTbnQ=p8Oz9893uVMJ1UpEQ@mail.gmail.com' \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@poorly.run \
/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).