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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B956DC433F5 for ; Sun, 2 Oct 2022 14:44:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229837AbiJBOoB (ORCPT ); Sun, 2 Oct 2022 10:44:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49268 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229777AbiJBOnx (ORCPT ); Sun, 2 Oct 2022 10:43:53 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DF62B1F2FC; Sun, 2 Oct 2022 07:43:37 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 85B45B80113; Sun, 2 Oct 2022 14:43:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4C425C433C1; Sun, 2 Oct 2022 14:43:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1664721815; bh=2yCQ4consgu91UPwtGrTfm09m9Fgk8nj9E8t0MeWwP4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=RsmgjSd+T+KhFIU/2gWac55p0w03CJ2F+b/HPi0IpCBEqqJDHotzDORKadJ+TGvcg nD7kvQ7gXsj7x/DI81RgjFiN4oEU5JjkYnAtirxYv4PF6mW9SgpGBGfTokVtKGu0Y8 PLxLn/rFPgB4PR7rct9hifye3Xts7Joo/dwezSiaAYeJgHuOXx1RsVFQnpOSd7eemf 4X+RW/mD0OzS9mDJViNth6F9GYFXf5N7/2jqtAJOV6MdnUkeSRPzqEiuPPSR+Kva5D ld3mSKp6aQP8Rip92KWJoySwe1Ao6OHIlD7i8BVBdTPpoOmG0dI3rBvdeH6M5Grpyl YSTmghwTeiN0A== Date: Sun, 2 Oct 2022 15:43:51 +0100 From: Jonathan Cameron To: Crt Mori Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, Andy Shevchenko Subject: Re: [PATCH v6 0/3] iio: temperature: mlx90632: Add powermanagement Message-ID: <20221002154351.4fb5c1ae@jic23-huawei> In-Reply-To: References: <20220924173221.1174608b@jic23-huawei> <20221002122535.07d66ab3@jic23-huawei> X-Mailer: Claws Mail 4.1.0 (GTK 3.24.34; 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-kernel@vger.kernel.org On Sun, 2 Oct 2022 16:36:39 +0200 Crt Mori wrote: > >> I sure hope you mean 6.1 material... It would be great to get into 6.0 > >> as i think that is a most likely candidate also for Android kernel > >> baseline (which is what I am also targeting). > > > > Sorry, I do mean 6.2. > > > > The merge window for 6.0 was months ago and we have to line 6.1 material > > up a week or so before the 6.1 merge window (which probably starts today). > > That allows us to get build bots and similar results before the merge window > > and with time to fix any issues. > > > > So unfortunately this will only be in a released kernel in about 6 months time: > > 3 months for the 6.1 cycle that this just missed and then it'll go into Linus' > > mainline tree, but the release will still be 3 months after that. > > > > In the meantime it'll be in linux-next from just after 6.1-rc1, and in > > Linus' tree for 6.2-rc1. > > > > Kernel cycles are short for a bit project, but they still have about > > 3 to 6 month delay for new code reaching a release. This just happened > > to hit the maximum. > > > > Jonathan > > OK, then fingers crossed we get rc8, as then I imagine you could put > this series into the 6.1 right? Would be really grateful if it would > not take 6 months to get this into mainline. Pretty unlikely as last Sunday Linus indicated that he was expecting to release new kernel today :( Note it'll be in mainline in 3 months, just not in a release because those take just under 3 months. Jonathan > > Crt > > On Sun, 2 Oct 2022 at 13:25, Jonathan Cameron wrote: > > > > On Mon, 26 Sep 2022 15:20:16 +0200 > > Crt Mori wrote: > > > > > On Sat, 24 Sept 2022 at 18:32, Jonathan Cameron wrote: > > > > > > > > > The sensor runtime suspension is set to MLX90632_SLEEP_DELAY_MS which is > > > > > hardcoded to 3 times as much as MEAS_MAX_TIME. > > > > > > > > > Hi Crt, > > > > > > > > Applied. However, we are cutting it very tight for the coming merge window > > > > so I'm not sure I'll get a 3rd pull request out (this just missed the 2nd > > > > one as I only queued up material that was in a final state last weekend) > > > > So for now pushed out as testing and we'll see if Linus hints at an rc8 > > > > when he releases rc7 tomorrow. If not this will be 6.2 material now. > > > > > > > I sure hope you mean 6.1 material... It would be great to get into 6.0 > > > as i think that is a most likely candidate also for Android kernel > > > baseline (which is what I am also targeting). > > > > Sorry, I do mean 6.2. > > > > The merge window for 6.0 was months ago and we have to line 6.1 material > > up a week or so before the 6.1 merge window (which probably starts today). > > That allows us to get build bots and similar results before the merge window > > and with time to fix any issues. > > > > So unfortunately this will only be in a released kernel in about 6 months time: > > 3 months for the 6.1 cycle that this just missed and then it'll go into Linus' > > mainline tree, but the release will still be 3 months after that. > > > > In the meantime it'll be in linux-next from just after 6.1-rc1, and in > > Linus' tree for 6.2-rc1. > > > > Kernel cycles are short for a bit project, but they still have about > > 3 to 6 month delay for new code reaching a release. This just happened > > to hit the maximum. > > > > Jonathan > > > > > > > > > > > Thanks, > > > > > > > > Jonathan > > > > > > > > > >