From: Jonathan Cameron <jic23@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Silvan Murer <silvan.murer@gmail.com>,
linux-iio@vger.kernel.org,
Maxime Roussin-Belanger <maxime.roussinbelanger@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Hartmut Knaack <knaack.h@gmx.de>,
kernel@pengutronix.de
Subject: Re: [PATCH 4/3] iio: dac: ltc2632: remove some unused defines
Date: Sat, 7 Mar 2020 11:17:55 +0000 [thread overview]
Message-ID: <20200307111755.51d1a4d9@archlinux> (raw)
In-Reply-To: <20200225093259.rx34tfu4yscfbmwq@pengutronix.de>
On Tue, 25 Feb 2020 10:32:59 +0100
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> On Thu, Feb 06, 2020 at 10:44:18AM +0000, Jonathan Cameron wrote:
> > On Thu, 6 Feb 2020 11:34:43 +0100
> > Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> >
> > > On Thu, Feb 06, 2020 at 10:29:15AM +0000, Jonathan Cameron wrote:
> > > > On Mon, 3 Feb 2020 21:31:26 +0100
> > > > Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> > > >
> > > > > These two defines are unused since the driver was introduced in commit
> > > > > 02b829f9e11f ("iio: dac: Add support for ltc2632 DACs").
> > > > >
> > > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > > A bit of fuzz and the mysterious bit of this being patch 4 of 3 aside all good.
> > > >
> > > > Applied to the togreg branch of iio.git and pushed out as testing.
> > >
> > > If you applied patches 2 and 3 of the series before, the fuzz should
> > > disappear. I assume the threading didn't work as intended for you and
> > > you don't have the original patch series grouped with my patch 4/3?
> > Yup. Just realised that after sending :)
> >
> > I'll apply them in the right order.
>
> Last time I already wondered why patches you applied don't appear in
> next. This had something to do with the workflow how patches go from you
> over Greg to Linus.
>
> Given that next is different and in my experience it is possible to get
> a tree into next even as a "second-level" maintainer, I wonder if adding
> your tree would be beneficial. You applied the patch more than two weeks
> ago and there is still no exposure to next. :-|
Ideally things would normally move quicker. I've been fighting off a
nasty and very persistent cold so running rather behind.
Agreed in theory it would make sense to take IIO directly into next,
but to do that the issue is that my availability can be rather intermittent
so I try to time pull requests to Greg for times when I can deal with any
fall out the over the next few days. It's not uncommon for there to be
problems and I hate to annoy people by not being able to sort them in
a timely fashion.
Anyhow, I'll look at it again sometime soon.
Jonathan
>
> Best regards
> Uwe
>
next prev parent reply other threads:[~2020-03-07 11:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 13:15 [PATCH 1/3] dt-bindings: iio: ltc2632: expand for ltc2636 support Uwe Kleine-König
2020-01-30 13:15 ` [PATCH 2/3] iio: dac: ltc2632: drop some duplicated data Uwe Kleine-König
2020-02-06 10:54 ` Jonathan Cameron
2020-01-30 13:15 ` [PATCH 3/3] iio: dac: ltc2632: add support for LTC2636 family Uwe Kleine-König
2020-02-02 9:54 ` Jonathan Cameron
2020-02-06 10:54 ` Jonathan Cameron
2020-02-02 9:52 ` [PATCH 1/3] dt-bindings: iio: ltc2632: expand for ltc2636 support Jonathan Cameron
2020-02-06 10:42 ` Jonathan Cameron
2020-02-03 20:31 ` [PATCH 4/3] iio: dac: ltc2632: remove some unused defines Uwe Kleine-König
2020-02-06 10:29 ` Jonathan Cameron
2020-02-06 10:34 ` Uwe Kleine-König
2020-02-06 10:44 ` Jonathan Cameron
2020-02-25 9:32 ` Uwe Kleine-König
2020-03-07 11:17 ` Jonathan Cameron [this message]
2020-02-06 18:11 ` [PATCH 1/3] dt-bindings: iio: ltc2632: expand for ltc2636 support Rob Herring
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=20200307111755.51d1a4d9@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.roussinbelanger@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=silvan.murer@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).