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=-15.5 required=3.0 tests=BAYES_00, INCLUDES_PULL_REQUEST,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,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 750CEC433ED for ; Wed, 7 Apr 2021 07:58:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 42A99611C1 for ; Wed, 7 Apr 2021 07:58:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235059AbhDGH7B (ORCPT ); Wed, 7 Apr 2021 03:59:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:39626 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229529AbhDGH7A (ORCPT ); Wed, 7 Apr 2021 03:59:00 -0400 Received: from jic23-huawei (cpc108967-cmbg20-2-0-cust86.5-4.cable.virginm.net [81.101.6.87]) (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 B32AE60BD3; Wed, 7 Apr 2021 07:58:50 +0000 (UTC) Date: Wed, 7 Apr 2021 08:59:07 +0100 From: Jonathan Cameron To: Greg KH Cc: linux-iio@vger.kernel.org Subject: Re: [PULL] 2nd set of IIO features and cleanup etc for 5.13 Message-ID: <20210407085907.0dd1e53b@jic23-huawei> In-Reply-To: <20210407084332.6ac35e61@jic23-huawei> References: <20210406220555.0d6bc9b6@jic23-huawei> <20210407084332.6ac35e61@jic23-huawei> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org On Wed, 7 Apr 2021 08:43:32 +0100 Jonathan Cameron wrote: > On Wed, 7 Apr 2021 08:35:41 +0200 > Greg KH wrote: > > > On Tue, Apr 06, 2021 at 10:05:55PM +0100, Jonathan Cameron wrote: > > > The following changes since commit 9c15db92a8e56bcde0f58064ac1adc28c0579b51: > > > > > > Merge tag 'iio-for-5.13a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next (2021-03-26 12:09:47 +0100) > > > > > > are available in the Git repository at: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.13b > > > > It looks like I had a minor cleanup fix to one of the files you removed > > from staging in my tree, but that was reasy to resolve. > > > > However, I got the following error when trying to push these out: > > > > Commit: b3c20190dd32 ("iio: Fix iio_read_channel_processed_scale()") > > Fixes tag: Fixes: dc98269f7c7d ("iio: Provide iio_read_channel_processed_scale() API") > > Has these problem(s): > > - Target SHA1 does not exist > > > > Where did that git commit id come from? > > There were a bunch of rebases earlier this cycle that must have crossed. > > Oddly the fixes checking script I've been using is happy with that > id but it's clearly wrong. *sigh* I'll have to take a closer look > at what it is doing. Sorry about that. > > Anyhow, rebased with that tag fixes and I'll send a new pull in a few minutes > > Jonathan As a side note on this, would you mind if I asked for linux-next to include the iio togreg and fixes-togreg branches directly? Might be good to benefit from the extra testing coverage that will give before I get anywhere near sending you a pull request. No replacement for local scripts but might pick up on when they go wrong as happened here. Jonathan > > > > > Can you fix that up please? > > > > thanks, > > > > greg k-h >