Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <gregkh@linuxfoundation.org>, <linux-iio@vger.kernel.org>
Subject: Re: [PULL] 1st set of IIO fixes for the 5.16 cycle (suggest queuing for merge window as nothing urgent)
Date: Fri, 22 Oct 2021 17:07:52 +0100	[thread overview]
Message-ID: <20211022170752.0000686c@Huawei.com> (raw)
In-Reply-To: <20211022162345.0000350c@Huawei.com>

On Fri, 22 Oct 2021 16:23:45 +0100
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:

> The following changes since commit 37f12202c5d28291ba5f83ce229771447ce9148f:
> 
>   staging: r8188eu: prevent array underflow in rtw_hal_update_ra_mask() (2021-10-05 12:35:30 +0200)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-5.16a
> 
> for you to fetch changes up to 486a25084155bf633768c26f022201c051d6fd95:
> 
>   iio: buffer: Fix memory leak in iio_buffers_alloc_sysfs_and_mask() (2021-10-21 10:26:38 +0100)
> 
> ----------------------------------------------------------------

Hi Greg,

Doesn't make much sense to rush this set in, so I'd suggest just merging
it alongside the other pull request to char-misc-next.

I thought about just merging this into the iio-togreg branch and
sending you one pull request, but decided this was simpler.  Let me know
if you'd prefer it done a different way.

*fingers crossed* I haven't messed these up this time!

The last few patches hit linux-next today but most in both these pull
requests have been soaking for a while.

Thanks,

Jonathan

> First set of IIO fixes for the 5.16 cycle
> 
> As these are very late in the 5.15 cycle and non are particularly urgent,
> they can wait for the merge window.
> 
> Key element in this set is Yang Yingliang has identified a number of
> issues in error paths introduced recently when we added multiple
> buffer support.
> 
> Other fixes:
> * adi,ad5662
>   - Fix handling of i2c_master_send() return value.
> * adi,ad5766
>   - Fix a wrong dt-property name that indicated wrong units and
>     did not mach the bindings.
>   - Associated 'fix' of the bindings example to have a possible scale.
> * st,pressure-spi
>   - Add some missing entries to the spi_device_id table to ensure
>     auto-loading works.
> * ti,tsc2046
>   - Fix a backwards comparison leading to a false dev_warn
> 
> ----------------------------------------------------------------
> Mark Brown (1):
>       iio: st_pressure_spi: Add missing entries SPI to device ID table
> 
> Mihail Chindris (2):
>       drivers: iio: dac: ad5766: Fix dt property name
>       Documentation:devicetree:bindings:iio:dac: Fix val
> 
> Oleksij Rempel (1):
>       iio: adc: tsc2046: fix scan interval warning
> 
> Pekka Korpinen (1):
>       iio: dac: ad5446: Fix ad5622_write() return value
> 
> Yang Yingliang (7):
>       iio: buffer: check return value of kstrdup_const()
>       iio: buffer: Fix memory leak in __iio_buffer_alloc_sysfs_and_mask()
>       iio: buffer: Fix double-free in iio_buffers_alloc_sysfs_and_mask()
>       iio: buffer: Fix memory leak in iio_buffer_register_legacy_sysfs_groups()
>       iio: core: check return value when calling dev_set_name()
>       iio: core: fix double free in iio_device_unregister_sysfs()
>       iio: buffer: Fix memory leak in iio_buffers_alloc_sysfs_and_mask()
> 
>  .../devicetree/bindings/iio/dac/adi,ad5766.yaml    |  2 +-
>  drivers/iio/adc/ti-tsc2046.c                       |  2 +-
>  drivers/iio/dac/ad5446.c                           |  9 ++++++-
>  drivers/iio/dac/ad5766.c                           |  6 ++---
>  drivers/iio/industrialio-buffer.c                  | 28 +++++++++++++---------
>  drivers/iio/industrialio-core.c                    |  9 ++++++-
>  drivers/iio/pressure/st_pressure_spi.c             |  4 ++++
>  7 files changed, 42 insertions(+), 18 deletions(-)


  reply	other threads:[~2021-10-22 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 15:23 [PULL] 1st set of IIO fixes for the 5.16 cycle (suggest queuing for merge window as nothing urgent) Jonathan Cameron
2021-10-22 16:07 ` Jonathan Cameron [this message]
2021-10-24 11:09   ` Greg KH
2021-10-24 11:09 ` Greg KH

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=20211022170752.0000686c@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=gregkh@linuxfoundation.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