linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of: Provide dummy of_device_compatible_match() for compile-testing
Date: Tue, 13 Jun 2017 12:32:22 +0200	[thread overview]
Message-ID: <CAMuHMdUwXXioxt8_nhDM0x1h=KBb6HnNgkzwdM-qGVy7cSNH9Q@mail.gmail.com> (raw)
In-Reply-To: <1493141928-29251-1-git-send-email-geert+renesas@glider.be>

On Tue, Apr 25, 2017 at 7:38 PM, Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Most of_device_*() functions have dummy versions for CONFIG_OF=n,
> but of_device_compatible_match() hasn't.  Fix that to improve the
> ability to do compile-testing.
>
> Fixes: b9c13fe32faaa71c ("dt: Add of_device_compatible_match()")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Any reason not to apply this patch?

Thanks!

> ---
>  include/linux/of.h | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/of.h b/include/linux/of.h
> index 21e6323de0f3b786..bfd1a23221735161 100644
> --- a/include/linux/of.h
> +++ b/include/linux/of.h
> @@ -620,6 +620,12 @@ static inline int of_device_is_compatible(const struct device_node *device,
>         return 0;
>  }
>
> +static inline  int of_device_compatible_match(struct device_node *device,
> +                                             const char *const *compat)
> +{
> +       return 0;
> +}
> +
>  static inline bool of_device_is_available(const struct device_node *device)
>  {
>         return false;
> --
> 2.7.4

  reply	other threads:[~2017-06-13 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 17:38 [PATCH] of: Provide dummy of_device_compatible_match() for compile-testing Geert Uytterhoeven
2017-06-13 10:32 ` Geert Uytterhoeven [this message]
2017-06-13 20:52   ` Rob Herring

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='CAMuHMdUwXXioxt8_nhDM0x1h=KBb6HnNgkzwdM-qGVy7cSNH9Q@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).