From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Rob Herring <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH] video: fbdev: Convert to using %pOF instead of full_name
Date: Mon, 07 Aug 2017 15:02:05 +0000 [thread overview]
Message-ID: <11214112.PD8VBvCJLW@amdc3058> (raw)
In-Reply-To: <CAL_JsqLy44aZdGcH7mGbmfQ49DTXU7fwoed8UCuaNEMVc_M8FQ@mail.gmail.com>
On Tuesday, August 01, 2017 12:24:53 PM Rob Herring wrote:
> On Tue, Aug 1, 2017 at 8:47 AM, Bartlomiej Zolnierkiewicz
> <b.zolnierkie@samsung.com> wrote:
> > On Tuesday, July 18, 2017 04:43:36 PM Rob Herring wrote:
> >> Now that we have a custom printf format specifier, convert users of
> >> full_name to use %pOF instead. This is preparation to remove storing
> >> of the full path string for each node.
> >>
> >> Signed-off-by: Rob Herring <robh@kernel.org>
> >> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> >> Cc: linux-fbdev@vger.kernel.org
> >
> > The patch Looks fine to me. Do you want me to merge it through fbdev
> > tree or do you have some other plan for %pOF conversion patches?
>
> Please take thru the fbdev tree.
Patch queued for 4.14, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2017-08-07 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170718214516epcas5p41593e7a72c2abb4ab7f78934027679fb@epcas5p4.samsung.com>
2017-07-18 21:43 ` [PATCH] video: fbdev: Convert to using %pOF instead of full_name Rob Herring
2017-08-01 13:47 ` Bartlomiej Zolnierkiewicz
2017-08-01 17:24 ` Rob Herring
2017-08-07 15:02 ` Bartlomiej Zolnierkiewicz [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=11214112.PD8VBvCJLW@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).