devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Peter Rosin <peda@axentia.se>
Cc: Andreas Klinger <ak@it-klinger.de>,
	jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, linux-iio@vger.kernel.org, wsa@the-dreams.de,
	robh+dt@kernel.org, mark.rutland@arm.com,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] iio: srf08: add support for similar devices and triggered buffers
Date: Thu, 17 Aug 2017 07:30:19 +0100	[thread overview]
Message-ID: <20170817073019.0000051c@huawei.com> (raw)
In-Reply-To: <823ea9d0-0410-2d6d-813b-686582656d68@axentia.se>

On Wed, 16 Aug 2017 22:14:33 +0200
Peter Rosin <peda@axentia.se> wrote:

> On 2017-08-16 21:32, Andreas Klinger wrote:
> > This patch series adds support for:
> > - triggered buffer
> > - ultrasonic devices srf02 and srf10
> > 
> > Thanks for the review of Peter and Wolfram.
> > 
> > @Wolfram: please let me know, if you want a separate patch for [PATCH 1/5]  
> 
> I think what you should do is rebase to something fresher, such as the
> togreg branch in the iio repo. As you have discovered, master branch is
> lagging behind in that repo.
> 
> And I think Jonathan would like that as well, but perhaps it doesn't
> make a difference for him?
Ah.. I always forget to do anything with the master branch.  Should bring it
up to date on mainline releases but never remember to do so.

The togreg branch is a better bet certainly.  Most of the time latest
round numbered release i.e. an rcX or final release of Linus' tree
is fine as well.  Occasionally multiple people are working on the same
driver but it's fairly rare within a cycle.

Depending on HK airport wifi later I might see if I can push out
something sensible as master.  I think the nice web interface will
get annoyed if I remove the master branch entirely...

Jonathan
> 
> Cheers,
> peda
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-08-17  6:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 19:32 [PATCH v3 0/5] iio: srf08: add support for similar devices and triggered buffers Andreas Klinger
2017-08-16 20:14 ` Peter Rosin
2017-08-17  6:30   ` Jonathan Cameron [this message]
2017-08-16 20:34 ` Wolfram Sang

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=20170817073019.0000051c@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=ak@it-klinger.de \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peda@axentia.se \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=wsa@the-dreams.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).