All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Iskren Chernev <iskren.chernev@gmail.com>
Cc: linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	devicetree@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH 1/3] regulator: max77826: Add max77826 regulator driver
Date: Tue, 14 Apr 2020 11:56:14 +0100	[thread overview]
Message-ID: <20200414105613.GA5412@sirena.org.uk> (raw)
In-Reply-To: <20200413164440.1138178-2-iskren.chernev@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 294 bytes --]

On Mon, Apr 13, 2020 at 07:44:38PM +0300, Iskren Chernev wrote:

> +static const struct of_device_id max77826_of_match[] = {
> +	{ .compatible = "maxim,max77826-regulator" },

This should just be maxim,max77826 - there's no need to disambiguate or
describe the device in the compatible string.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-04-14 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 16:44 [PATCH 0/3] regulator: max77826: Add MAX77826 support Iskren Chernev
2020-04-13 16:44 ` [PATCH 1/3] regulator: max77826: Add max77826 regulator driver Iskren Chernev
2020-04-14 10:56   ` Mark Brown [this message]
2020-04-13 16:44 ` [PATCH 2/3] dt-bindings: regulator: Add document bindings for max77826 Iskren Chernev
2020-04-20 20:55   ` Rob Herring
2020-04-23 12:59     ` Iskren Chernev
2020-04-24 14:28       ` Rob Herring
2020-04-13 16:44 ` [PATCH 3/3] ARM: dts: qcom: msm8974-klte: Add max77826 pmic node Iskren Chernev
2020-04-14 10:57 ` [PATCH 0/3] regulator: max77826: Add MAX77826 support Mark Brown
2020-04-14 13:14   ` Iskren Chernev
2020-04-14 14:53     ` Mark Brown

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=20200414105613.GA5412@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=iskren.chernev@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.