All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] 2nd set of IIO fixes for the 6.6 cycle (probably for 6.7 merge window given timing)
Date: Sat, 21 Oct 2023 17:36:59 +0200	[thread overview]
Message-ID: <2023102131-mocker-unfreeze-e4d6@gregkh> (raw)
In-Reply-To: <20231021155727.511a344c@jic23-huawei>

On Sat, Oct 21, 2023 at 03:57:27PM +0100, Jonathan Cameron wrote:
> The following changes since commit ffd1f150fffe8a708f6ccd15152791d0e8f812b6:
> 
>   Merge tag 'iio-fixes-for-6.6a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into char-misc-linus (2023-10-06 16:58:28 +0200)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-6.6b
> 
> for you to fetch changes up to bee448390e5166d019e9e037194d487ee94399d9:
> 
>   iio: afe: rescale: Accept only offset channels (2023-10-17 20:25:32 +0100)
> 
> ----------------------------------------------------------------
> 2nd set of IIO fixes for the 6.6 cycle.
> 
> Note, given timing my expectation is these will be queued for the
> 6.7 merge window but they could go quicker if the 6.6 cycle ends up
> being extended.

Let's see how long the cycle takes, I've pulled this into my "to linus"
branch for now, thanks!

greg k-h

      reply	other threads:[~2023-10-21 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 14:57 [PULL] 2nd set of IIO fixes for the 6.6 cycle (probably for 6.7 merge window given timing) Jonathan Cameron
2023-10-21 15:36 ` Greg KH [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=2023102131-mocker-unfreeze-e4d6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    /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.