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 6BF82ECAAD5 for ; Fri, 2 Sep 2022 19:42:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229785AbiIBTmE (ORCPT ); Fri, 2 Sep 2022 15:42:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41010 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229496AbiIBTmD (ORCPT ); Fri, 2 Sep 2022 15:42:03 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 979C3FCA1A for ; Fri, 2 Sep 2022 12:42:02 -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 dfw.source.kernel.org (Postfix) with ESMTPS id 1F4BE60F63 for ; Fri, 2 Sep 2022 19:42:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 06979C433D6; Fri, 2 Sep 2022 19:41:59 +0000 (UTC) Date: Fri, 2 Sep 2022 20:41:56 +0100 From: Catalin Marinas To: Mark Brown Cc: Will Deacon , Shuah Khan , Marc Zyngier , Mark Rutland , Zhang Lei , linux-kselftest@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3 0/3] arm64/sve: Document our actual SVE syscall ABI Message-ID: References: <20220829162502.886816-1-broonie@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org On Fri, Sep 02, 2022 at 07:57:15PM +0100, Mark Brown wrote: > On Fri, Sep 02, 2022 at 07:22:20PM +0100, Catalin Marinas wrote: > > On Mon, Aug 29, 2022 at 05:24:59PM +0100, Mark Brown wrote: > > > v3: > > > - Rebase onto v6.0-rc3. > > > v2: > > > - Rebase onto v6.0-rc1. > > > Please don't rebase beyond -rc1 unless it no longer applies cleanly. I > > came back from holiday and I have two or three versions of all of your > > patches in my inbox. It just adds to the clutter. > > OK, sure. It might help to advertise what you're looking for here - the > whole thing with wanting everything based off -rc3 has never been clear > to me, IIRC I figured it out from some off hand comment rather than > actually knowing what you and Will want. It's neither base off latest > nor base off -rc1 which seem to be the more common policies. Usually basing off -rc1 is sufficient unless the patches conflict with something newer and we occasionally push for-next/core to even higher -rcX. Of course, fixes for something in a late -rc should be based off that version. Both Will and I start queuing patches around -rc3 with the two weeks before pretty much reviewing or waiting to see if there are any more comments. I don't mind you basing your patches off -rc3 though in general it's better for series aimed at the upcoming merging window to be posted shortly after -rc1 to give them some more time on the list. However, once posted, if there are no changes please don't repost them for subsequent -rcX, it won't make any difference as we can just apply the original series to whatever we base for-next/core off. Thanks. -- Catalin