All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dylan Laduranty <dylan.laduranty@mesotic.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Sa, Nuno" <Nuno.Sa@analog.com>
Subject: Re: [PATCH 2/2 v3] dt-bindings: ADAU7118: add new entries for pins drive strength
Date: Tue, 17 May 2022 10:40:26 +0200	[thread overview]
Message-ID: <1816957.tdWV9SEqCh@localhost.localdomain> (raw)
In-Reply-To: <PH0PR03MB6786A29EE38C9FDF74B4F02299CE9@PH0PR03MB6786.namprd03.prod.outlook.com>

Hi Nuno,

> Hi Dylan,
> 
> > -----Original Message-----
> > From: Dylan Laduranty <dylan.laduranty@mesotic.com>
> > Sent: Tuesday, May 17, 2022 7:48 AM
> > To: alsa-devel@alsa-project.org
> > Cc: Sa, Nuno <Nuno.Sa@analog.com>; Dylan Laduranty
> > <dylan.laduranty@mesotic.com>
> > Subject: [PATCH 2/2 v3] dt-bindings: ADAU7118: add new entries for
> > pins drive strength
> > 
> > [External]
> > 
> > Update driver doc with new entries for managing pins drive strength.
> > Add a table to describe possible values for each entry.
> > 
> > Signed-off-by: Dylan Laduranty <dylan.laduranty@mesotic.com>
> > ---
> 
> Just a note for the future. In my previous review I said something
> like:
> 
> "
> ... With that fixed:
> 
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> "
> 
> Hence, you could/should have included my 'Reviewed-by' tag in v3.
I apologize, this is my first contribution to Linux kernel so I am not 
comfortable with this yet. I'll resend this serie later today.

> 
> - Nuno Sá

Dylan Laduranty





  reply	other threads:[~2022-05-17  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17  5:48 [PATCH 1/2 v3] ASoC: ADAU7118: add bindings for managing pins drive strength Dylan Laduranty
2022-05-17  5:48 ` [PATCH 2/2 v3] dt-bindings: ADAU7118: add new entries for " Dylan Laduranty
2022-05-17  8:18   ` Sa, Nuno
2022-05-17  8:40     ` Dylan Laduranty [this message]
2022-05-17  8:43       ` Sa, Nuno

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=1816957.tdWV9SEqCh@localhost.localdomain \
    --to=dylan.laduranty@mesotic.com \
    --cc=Nuno.Sa@analog.com \
    --cc=alsa-devel@alsa-project.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 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.