Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org,
	Olivier Moysan <olivier.moysan@foss.st.com>,
	Paul Cercueil <paul@crapouillou.net>,
	Nuno Sa <nuno.sa@analog.com>
Subject: Re: IIO this cycle.
Date: Mon, 28 Aug 2023 19:23:50 +0100	[thread overview]
Message-ID: <20230828192350.66f2aec8@jic23-huawei> (raw)
In-Reply-To: <20230809182331.18c259c5@jic23-huawei>

On Wed, 9 Aug 2023 18:23:31 +0100
Jonathan Cameron <jic23@kernel.org> wrote:

> Hi All,
> 
> I'm going to be travelling without a laptop next week so won't be sending
> my usual last minute second pull request to pick up the stuff that just
> squeaked over the line time wise.
> 
> As such I'm sorry to say the IIO tree is effectively closed for the 6.6
> merge window a week early as I won't be back online until after rc7.
> 
> I might queue up a few things over next few days but, with the exception
> of fixes, they will be targeting the 6.7 cycle.
> 
> Thanks,
> 
> Jonathan

Back in action (more or less :)  I think I caught up with what I'd consider
the 'normal' stuff mostly today.  There are a few series waiting for trees
to advance during the merge window (fixes for recent stuff mostly)

Otherwise it's the interesting series that are outstanding :)

iio: Add buffer write() support
Add converter framework
iio: Add iio backend device type

I'll try and take a first look at least in the next week.

Jonathan

      reply	other threads:[~2023-08-28 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 17:23 IIO this cycle Jonathan Cameron
2023-08-28 18:23 ` 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=20230828192350.66f2aec8@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=paul@crapouillou.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