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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 5686CC74A5B for ; Fri, 17 Mar 2023 14:49:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=M3b5kz3Rm9Y64lMlqSUulhLUYChJaYm5aXfD/O7Yk7Y=; b=vK1YKUGXEWA1TR A+I0jYQE5IE3yJgG1FZEs006zLOy3KMTik6WTEPThQD+q1LaKmlWtqRFoYuZMIMajCUtoxfqbuo+O YzJ7q75oYwbuJ6oI9ifeJF/0bZw4QqQeg7Q+zo4TSR70r5iqM54F+uciTr11lytEq7ema/9ctFfL4 8Yltfs3wY6TJh3imfHchE80nOOAA0yO6Euezuhw+vV3Kp79tFskyaoxOOhbYNERjYeicTJT0Snt5z EM4bcXTZb5p9tpY1sUsS7Gx/NYcKCYEVuLo2KoFbDgbCDoYFvNiEVFvqhDgFNbp+i+cOywcEVfW/x VMsetubNZFvTmdqXoNTg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1pdBNM-002Uin-2V; Fri, 17 Mar 2023 14:48:12 +0000 Received: from mail-qv1-xf35.google.com ([2607:f8b0:4864:20::f35]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1pdBNI-002Ui6-0D for linux-arm-kernel@lists.infradead.org; Fri, 17 Mar 2023 14:48:09 +0000 Received: by mail-qv1-xf35.google.com with SMTP id f1so3555260qvx.13 for ; Fri, 17 Mar 2023 07:48:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1679064486; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=Y00W2vlLuMTbF2Huj0Es001wY7aldQjIanbtN1YOkHg=; b=GkkJPsXsxAnJCR1XPtQdP3YFkyJOXudoVpKmeyKidWxq5/F+DaHJ50CBo/SM2CWZkd q0OfIHgh3368j1WUWO3ddvm5pg1ZPrQ7Y25LxtVhO5uIs+c4Z17ucftFryTjJES78N04 41InlRoIBySZWbfAhx443i5LGCYhFQQKuCerE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679064486; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Y00W2vlLuMTbF2Huj0Es001wY7aldQjIanbtN1YOkHg=; b=Er0aqK3JYCrWITc00hn50ZJaqMDDm66dD+sGAeeZqqT9dV5iOn+UyaSKyns/Ev4dNQ 3yJr6S5HzV4HxW8591tBsyEeAsNl+VwWxwn6+svV9Dl7D370pQBaiOo3WxGTrBg1WRjF XnhCk37e6CTYn9LFpNdbk+69a8HF+flYasllOegHMhf4iUf4Sl8dx2isGUKxI5PrRxu4 nQvwCd1+cu/iI9VAIs7Fm5X6SHjW8qF5XSuWWW3ldnRYgXluCTXUChG124aKO+zXKZbV t2arRVBYfX4Dp3TIPb8fNKuvri2czQya1ZDJHnP785e91yayoPry5OxV7M1YHZg457LW PgBQ== X-Gm-Message-State: AO0yUKW/j3wSbyrTDRF/sEVeWXP7PNYdQScbMxfD4SCbv6J4909B4FyX YtCPqIRRj99LQtmsDaiFhxc3Sg== X-Google-Smtp-Source: AK7set/8JqWEiXgvw/KNL4eR/Drm+OM2J6X6b3kpVOvGlbkjiNe1G4th6mtxiSnoXVzd/sVarz3FZw== X-Received: by 2002:a05:6214:528e:b0:5a1:d92e:5cb2 with SMTP id kj14-20020a056214528e00b005a1d92e5cb2mr23731115qvb.10.1679064486364; Fri, 17 Mar 2023 07:48:06 -0700 (PDT) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-30-209-226-106-7.dsl.bell.ca. [209.226.106.7]) by smtp.gmail.com with ESMTPSA id x1-20020ac84a01000000b003d4008dccb7sm1408824qtq.48.2023.03.17.07.48.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 Mar 2023 07:48:05 -0700 (PDT) Date: Fri, 17 Mar 2023 10:48:03 -0400 From: Konstantin Ryabitsev To: Ira Weiny Cc: Michael Ellerman , Dave Hansen , Dave Hansen , Thomas Gleixner , Nicholas Piggin , Christophe Leroy , Catalin Marinas , Will Deacon , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H. Peter Anvin" , Dan Williams , Al Viro , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 0/3] COVER: Remove memcpy_page_flushcache() Message-ID: <20230317144803.kktahbp4fhmkutsq@meerkat.local> References: <20221230-kmap-x86-v1-0-15f1ecccab50@intel.com> <3523ddf9-03f5-3179-9f39-cec09f79aa97@intel.com> <64126d113d163_2595222942@iweiny-mobl.notmuch> <87lejxmax8.fsf@mpe.ellerman.id.au> <641340e2998b4_2695182944f@iweiny-mobl.notmuch> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <641340e2998b4_2695182944f@iweiny-mobl.notmuch> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230317_074808_638385_5F747074 X-CRM114-Status: GOOD ( 19.56 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Mar 16, 2023 at 09:16:34AM -0700, Ira Weiny wrote: > > It's also much easier to run git-send-email HEAD^^^, rather than running > > it three separate times, let alone if it's a 20 patch series. > > Exactly. And I'm using b4 which would have forced me to create a separate > branch for each of the patches to track. So I was keeping them around in > a single branch to let 0day run after the merge window. Then I forgot > about the idea of splitting them because b4 had it all packaged up nice! > > > > > I wonder if we could come up with some convention to indicate that a > > series is made up of independent patches, and maintainers are free to > > pick them individually - but still sent as a single series. > > Maybe. But perhaps b4 could have a send option which would split them > out? I'll see about adding an option to b4 but I've Cc'ed Konstantin as > well for the idea. Yes, I plan to introduce the concept of "bundles" in addition to "series". The distinction is that when you send a bundle, each patch is sent as individual submission and we generate the change-id for each patch. It's a bit more work to send a v2 of some patch (you have to do a "prep -n --from-thread "), but it's not insurmountable and should help with queuing up individual patches for sending post merge-window, like in your case. -K _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel