From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-12.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PULL_REQUEST,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_2 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 16C19C32771 for ; Sun, 12 Jan 2020 11:47:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D83FF214AF for ; Sun, 12 Jan 2020 11:46:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1578829619; bh=BhIJihXsW10fsJFjGU2yNcEQ5y2j0/ACrW9t2Uu/WQo=; h=Date:From:To:Subject:In-Reply-To:References:List-ID:From; b=ZDH0RKy7UeVXpMaNdsl2D/5fkI6FzzOIozx/Oek35W4vw/qhICox702CyRWEsMi7w q53s/pepTbBz0RF/S6ixeTMSHrRWZdibWT83MiZXzNT+pwFhcT1V5bbx9BAIWWuA9l kvpmA0xX6iMvufniDR4GmYs3F4fVlLJEMBHoz3KU= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732724AbgALLq6 (ORCPT ); Sun, 12 Jan 2020 06:46:58 -0500 Received: from mail.kernel.org ([198.145.29.99]:36350 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732707AbgALLq6 (ORCPT ); Sun, 12 Jan 2020 06:46:58 -0500 Received: from archlinux (cpc149474-cmbg20-2-0-cust94.5-4.cable.virginm.net [82.4.196.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 57BD1214AF; Sun, 12 Jan 2020 11:46:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1578829617; bh=BhIJihXsW10fsJFjGU2yNcEQ5y2j0/ACrW9t2Uu/WQo=; h=Date:From:To:Subject:In-Reply-To:References:From; b=zaDPHJNFBay+Vv7gy2isxRB3rkwp0iOFL8Aot0CCGkzCFbrFcMOL+/xa6YfYhzgnS qj7jBWu7ObMRScYWEu02vrYnGcTI+iGlwCQ4p6r3aeQopt7pE+w4V6T8sOU1htWVHV M5buMQ4Oc/hl7MBDq+//Ql+1WNTGc6OFutJ6welI= Date: Sun, 12 Jan 2020 11:46:53 +0000 From: Jonathan Cameron To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org Subject: Re: [PULL] Second set of IIO fixes for the 5.5 cycle. Message-ID: <20200112114653.01370ef8@archlinux> In-Reply-To: <20200105110051.445c9a95@archlinux> References: <20200105110051.445c9a95@archlinux> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-iio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org Hi Greg, Just wondering if this one slipped through the net? If we are cutting it a bit fine for the upcoming merge window then I'm happy if you want to apply these to your staging/staging-next tree instead of staging/staging-linus. Thanks, Jonathan On Sun, 5 Jan 2020 11:00:51 +0000 Jonathan Cameron wrote: > The following changes since commit c05c403b1d123031f86e65e867be2c2e9ee1e7= e3: >=20 > staging: wfx: fix wrong error message (2019-12-18 15:51:06 +0100) >=20 > are available in the Git repository at: >=20 > git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fi= xes-for-5.5b >=20 > for you to fetch changes up to 80d92ea5f865175bf4cb2cb252b0d1f439c4bcec: >=20 > iio: light: vcnl4000: Fix scale for vcnl4040 (2019-12-30 16:48:13 +0000) >=20 > ---------------------------------------------------------------- > 2nd Set of IIO fixes for the 5.5 cycle. >=20 > * Core > - Fix buffer alignment calculation. The previous logic meant that scans > could under some circumstances not have naturally aligned elements. > In theory someone might have been working around this in userspace, b= ut > if so we'd have expected them to query this very odd behaviour. > It's not hit in that many drivers as requires a mixture of channel > resolutions broad enough to require different packing. The one obvio= us > case of timestamps was fine under existing code as they are always the > last element if enabled and that was handled correctly. > * ad7124 > - DT channel configuration wasn't using the reg value so would lead > to some odd mappings and readout of the wrong channels. > * pms7003 > - Kconfig didn't specify triggered buffer dependency. > * st_lsm6dsx > - For the LSM6DS3 the id match wasn't working. > * vcnl4000 > - Scale was wrong for the vcnl4040 >=20 > ---------------------------------------------------------------- > Alexandru Tachici (1): > iio: adc: ad7124: Fix DT channel configuration >=20 > Guido G=C3=BCnther (1): > iio: light: vcnl4000: Fix scale for vcnl4040 >=20 > Lars M=C3=B6llendorf (1): > iio: buffer: align the size of scan bytes to size of the largest el= ement >=20 > Stephan Gerhold (1): > iio: imu: st_lsm6dsx: Fix selection of ST_LSM6DS3_ID >=20 > Tomasz Duszynski (1): > iio: chemical: pms7003: fix unmet triggered buffer dependency >=20 > drivers/iio/adc/ad7124.c | 12 +++++------- > drivers/iio/chemical/Kconfig | 1 + > drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 3 ++- > drivers/iio/industrialio-buffer.c | 6 +++++- > drivers/iio/light/vcnl4000.c | 3 ++- > 5 files changed, 15 insertions(+), 10 deletions(-)