All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"arnd@arndb.de" <arnd@arndb.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: No pull request for IIO this merge window (out of staging)
Date: Sat, 07 Jan 2012 10:07:51 +0000	[thread overview]
Message-ID: <4F081977.2000807@cam.ac.uk> (raw)


I thought I should write a quick email updating people on the current
situation.

Original plan was to send Linus a pull request for the basic core
support and 'pull' in-kernel interfaces.  When I backported the 'pull'
in-kernel interfaces to the staging tree (for speed they had been
developed against the simpler core support rather than the main version
of IIO in staging - seemed a good idea at the time), Greg KH took a look
and has raised some significant issues that we still need to address.
The sticky point is a disagreement about the best means of handling
mappings between channels on a child device and the IIO device.

Hence I have no intention of sending Linus a pull request for moving
any of IIO out of staging until these issues have been sorted out.

Saddly my time has now become rather more restricted so I am taking
longer to persue these issues.  Things aren't too bad as others have
stepped up to assist with the day to day burden of patch review and work
on the staging tree (thanks!).

Anyhow there have been lots of nice cleanups of the staging tree and
new work there, so it's not as though things aren't progressing. They
merely aren't going entirely according to plan!  Lots of good work
coming from Lars-Peter at ADI in particular. We also have our first SoC
adc driver from Maxime Ripard and some TI discrete device support from
Duss Pirmin.

Thanks

Jonathan


                 reply	other threads:[~2012-01-07 10:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F081977.2000807@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Michael.Hennerich@analog.com \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gregkh@suse.de \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    /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.