mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "tachicialex@gmail.com" <tachicialex@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: "jic23@kernel.org" <jic23@kernel.org>
Subject: Re: [PATCH 0/2] iio: dac: ad5770r: dt bindings fixes
Date: Sat, 21 Mar 2020 07:17:30 +0000	[thread overview]
Message-ID: <5a7729473f13cd7e9991b1ce0c1567d770eeb3e3.camel@analog.com> (raw)
In-Reply-To: <20200320160531.23732-1-alexandru.tachici@analog.com>

On Fri, 2020-03-20 at 18:05 +0200, Alexandru Tachici wrote:
> [External]
> 
> This aims to replace use of num property from dt nodes with
> reg property both in dt bindings and driver and fix
> dt bindings errors.
> 

Maybe do a RESEND for this and add
--to=devicetree@vger.kernel.org --cc=robh+dt@kernel.org
to the git send-mail command

Specifically for this, the DT list should be addressed.
But [naturally] the IIO list should also be included.


> 1. read from fwnode reg property instead of num property
> 
> 2. replace num property with reg property and fix dt
> bindings errors
> 
> Alexandru Tachici (2):
>   iio: dac: ad5770r: read channel nr from reg
>   dt-bindings: iio: dac: AD5570R fix bindings errors
> 
>  .../bindings/iio/dac/adi,ad5770r.yaml         | 77 ++++++++++---------
>  drivers/iio/dac/ad5770r.c                     |  2 +-
>  2 files changed, 41 insertions(+), 38 deletions(-)
> 

  parent reply	other threads:[~2020-03-21  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 16:05 Alexandru Tachici
2020-03-20 16:05 ` [PATCH 1/2] iio: dac: ad5770r: read channel nr from reg Alexandru Tachici
2020-03-20 16:05 ` [PATCH 2/2] dt-bindings: iio: dac: AD5570R fix bindings errors Alexandru Tachici
2020-03-21  7:17 ` Ardelean, Alexandru [this message]
2020-03-21 17:27   ` [PATCH 0/2] iio: dac: ad5770r: dt bindings fixes Jonathan Cameron

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=5a7729473f13cd7e9991b1ce0c1567d770eeb3e3.camel@analog.com \
    --to=alexandru.ardelean@analog.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tachicialex@gmail.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

all inboxes | Powered by JetHome®