linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Daniel Mack <daniel@zonque.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	"Andrew F. Davis" <afd@ti.com>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/2] drivers: misc: ti_dac7512: Remove duplicate driver
Date: Sun, 10 Sep 2017 20:43:15 +0200	[thread overview]
Message-ID: <20170910184315.GA13239@wunner.de> (raw)
In-Reply-To: <20170910161928.2b49d134@archlinux>

On Sun, Sep 10, 2017 at 04:19:28PM +0100, Jonathan Cameron wrote:
> On Tue, 5 Sep 2017 15:01:08 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tue, Sep 5, 2017 at 12:28 PM, Daniel Mack <daniel@zonque.org> wrote:
> > > That's true, but the devices that do are EOL for a long time, and they
> > > don't use mainline kernels anyway, for multiple reasons. So that
> > > shouldn't constrain us, and I'm all for replacing that driver with
> > > something that has a real infrastructure.
> > >
> > >   Acked-by: Daniel Mack <daniel@zonque.org>  
> > 
> > Ok, thanks for the confirmation. That's probably good enough to apply the
> > patch for 4.15. If someone else uses the driver without you knowing, they
> > can always complain later on and we revert the patch or think of an
> > alternative, but that seems unlikely.
> 
> Sounds good to me.  I'll pick it up through IIO given the small changes
> there and the fact you are happy with it.  Shout if you would prefer
> a different route. Given timing I won't be pushing this out on a non
> rebasing tree for a week or so anyway.
> 
> Applied to the togreg branch of iio.git and pushed out as testing for
> autobuilders to play with it.

Thank you Daniel, Arnd & Jonathan!

A minor note, the commit as pushed to iio.git/testing is missing Arnd's
Acked-by.  Also, the Cc: to Daniel is redundant given his ack.

Have a pleasant week,

Lukas

  reply	other threads:[~2017-09-10 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05  9:44 [PATCH 1/2] iio: dac: ad5446: Add IDs of compatible Texas Instruments chips Lukas Wunner
2017-09-05  9:44 ` [PATCH 2/2] drivers: misc: ti_dac7512: Remove duplicate driver Lukas Wunner
2017-09-05  9:56   ` Arnd Bergmann
2017-09-05 10:11     ` Lukas Wunner
2017-09-05 10:28       ` Daniel Mack
2017-09-05 13:01         ` Arnd Bergmann
2017-09-10 15:19           ` Jonathan Cameron
2017-09-10 18:43             ` Lukas Wunner [this message]
2017-09-11  8:41               ` Jonathan Cameron
2017-09-12 10:12                 ` Jonathan Cameron
2017-09-10 15:14 ` [PATCH 1/2] iio: dac: ad5446: Add IDs of compatible Texas Instruments chips 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=20170910184315.GA13239@wunner.de \
    --to=lukas@wunner.de \
    --cc=Michael.Hennerich@analog.com \
    --cc=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=daniel@zonque.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --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).