Linux IIO development
 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] IIO: 1st set of new device support, features and cleanup for 6.14
Date: Sun, 12 Jan 2025 13:47:32 +0100	[thread overview]
Message-ID: <2025011208-glider-happening-f481@gregkh> (raw)
In-Reply-To: <20250111132110.0b2d4fa2@jic23-huawei>

On Sat, Jan 11, 2025 at 01:21:10PM +0000, Jonathan Cameron wrote:
> The following changes since commit cdd30ebb1b9f36159d66f088b61aee264e649d7a:
> 
>   module: Convert symbol namespace to string literal (2024-12-02 11:34:44 -0800)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-6.14a

Pulled and pushed out.

> for you to fetch changes up to 577a66e2e634f712384c57a98f504c44ea4b47da:
> 
>   iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (2025-01-04 14:48:17 +0000)
> 
> ----------------------------------------------------------------
> IIO: 1st set of new device support, features and cleanup for 6.14
> 
> Fairly quiet cycle. Usual mix of new drivers, device support in
> existing drivers, features and more general rework and cleanup.
> There are a few late breaking or long standing but complex fixes
> in here as well.
> 
> There is one expected merge conflict due to an upstream fix touching
> neighboring code in ti-ads1119. The trivial resolution is the right one with
> the result ending up as:
> 
> 	struct {
> 		s16 sample;
> 		aligned_s64 timestamp;
> 	} scan;

I'll save this for later if it comes up, it didn't when I pulled this.

thanks,

greg k-h

      reply	other threads:[~2025-01-12 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11 13:21 [PULL] IIO: 1st set of new device support, features and cleanup for 6.14 Jonathan Cameron
2025-01-12 12:47 ` 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=2025011208-glider-happening-f481@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox