linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Peter Rosin <peda@axentia.se>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: dpot-dac: fix code comment in dpot_dac_read_raw()
Date: Sat, 29 Aug 2020 16:52:49 +0100	[thread overview]
Message-ID: <20200829165249.416b2efa@archlinux> (raw)
In-Reply-To: <20200826192529.GC2671@embeddedor>

On Wed, 26 Aug 2020 14:25:29 -0500
"Gustavo A. R. Silva" <gustavoars@kernel.org> wrote:

> On Wed, Aug 26, 2020 at 04:16:23PM +0200, Peter Rosin wrote:
> > On 2020-08-26 16:17, Gustavo A. R. Silva wrote:  
> > >> And just to be explicit, this fix is for 5.9.
> > >>
> > >> Acked-by: Peter Rosin <peda@axentia.se>
> > >>  
> > > 
> > > If you don't mind I can add this to my tree for 5.9-rc4
> > > and send it directly to Linus.  
> > 
> > Fine by me, Jonathan might think differently but I can't find a reason why.
> > Just about nothing is happening in that file and the risk for conflicts is
> > negligible.
> >   
> 
> OK. In the meantime, I have added this to my -next tree and queued it up
> for 5.9-rc3.
Absolutely fine by me.

Thanks,

Jonathan

> 
> Thanks
> --
> Gustavo


      reply	other threads:[~2020-08-29 15:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26  0:08 [PATCH] iio: dpot-dac: fix code comment in dpot_dac_read_raw() Gustavo A. R. Silva
2020-08-26  7:04 ` Peter Rosin
2020-08-26 14:17   ` Gustavo A. R. Silva
2020-08-26 14:16     ` Peter Rosin
2020-08-26 19:25       ` Gustavo A. R. Silva
2020-08-29 15:52         ` Jonathan Cameron [this message]

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=20200829165249.416b2efa@archlinux \
    --to=jic23@kernel.org \
    --cc=gustavo@embeddedor.com \
    --cc=gustavoars@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=pmeerw@pmeerw.net \
    /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).