From: Tejun Heo <tj@kernel.org>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
"\"open list:LIBATA PATA DRIVERS\"" <linux-ide@vger.kernel.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] pata_octeon_cf: use of_property_read_{bool|u32}()
Date: Mon, 28 Aug 2017 10:45:03 -0700 [thread overview]
Message-ID: <20170828174502.GX491396@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20170827195613.904715064@cogentembedded.com>
On Sun, Aug 27, 2017 at 10:55:09PM +0300, Sergei Shtylyov wrote:
> The Octeon CF driver basically open-codes of_property_read_{bool|u32}()
> using of_{find|get}_property() calls in its probe() method. Using the
> modern DT APIs saves 2 LoCs and 16 bytes of object code (MIPS gcc 3.4.3).
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Applied to libata/for-4.14.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-08-28 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 19:55 [PATCH] pata_octeon_cf: use of_property_read_{bool|u32}() Sergei Shtylyov
2017-08-28 17:45 ` Tejun Heo [this message]
2017-08-28 21:52 ` David Daney
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=20170828174502.GX491396@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=sergei.shtylyov@cogentembedded.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