linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Support RTC charging on PFUZE100
Date: Wed, 14 Nov 2018 14:25:28 -0800	[thread overview]
Message-ID: <20181114222528.GE2089@sirena.org.uk> (raw)
In-Reply-To: <20181030143718.10027-1-aford173@gmail.com>

On Tue, Oct 30, 2018 at 09:37:18AM -0500, Adam Ford wrote:
> 
> diff --git a/arch/arm/boot/dts/imx6-logicpd-som.dtsi b/arch/arm/boot/dts/imx6-logicpd-som.dtsi
> index 1e5dcac70045..74ab5d65106b 100755
> --- a/arch/arm/boot/dts/imx6-logicpd-som.dtsi
> +++ b/arch/arm/boot/dts/imx6-logicpd-som.dtsi

> diff --git a/drivers/regulator/pfuze100-regulator.c b/drivers/regulator/pfuze100-regulator.c
> index 659e516455be..bdef74077d1c 100644
> --- a/drivers/regulator/pfuze100-regulator.c
> +++ b/drivers/regulator/pfuze100-regulator.c

Please follow the patch submission process covered in
submitting-patchest.rst.  You've not included a Signed-off-by which is
essential for legal reasons as covered in there and this is a single
patch which mixes a DT change and a regulator driver change which should
be in separate patches.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20181114/f0c8519c/attachment.sig>

  reply	other threads:[~2018-11-14 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 14:37 [PATCH] Support RTC charging on PFUZE100 Adam Ford
2018-11-14 22:25 ` Mark Brown [this message]
2018-11-19 20:29   ` Adam Ford
2018-11-23 13:11     ` 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=20181114222528.GE2089@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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).