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 CC04AEE49A3 for ; Tue, 22 Aug 2023 09:51:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234503AbjHVJvL (ORCPT ); Tue, 22 Aug 2023 05:51:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59996 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232971AbjHVJvK (ORCPT ); Tue, 22 Aug 2023 05:51:10 -0400 Received: from 1wt.eu (ded1.1wt.eu [163.172.96.212]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 21A551B2; Tue, 22 Aug 2023 02:51:03 -0700 (PDT) Received: (from willy@localhost) by mail.home.local (8.17.1/8.17.1/Submit) id 37M9oC8O023548; Tue, 22 Aug 2023 11:50:12 +0200 Date: Tue, 22 Aug 2023 11:50:12 +0200 From: Willy Tarreau To: Christian Brauner Cc: Shuah Khan , "Paul E. McKenney" , Thomas =?iso-8859-1?Q?Wei=DFschuh?= , Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: duplicate patch in the nolibc tree Message-ID: References: <20230817133811.0a73c624@canb.auug.org.au> <9cfb4fe4-162b-3f26-646b-71bed3493925@linuxfoundation.org> <4c037ef2-9159-4528-8ecb-8596cb2a3889@paulmck-laptop> <20230817193909.GA30505@1wt.eu> <01d517c4-d91b-4426-b7f2-2b1277f21d8c@paulmck-laptop> <20230818-anblicken-mitinhaber-11cd07cce0a1@brauner> <6822c914-4f11-be93-ed55-56447a5838f9@linuxfoundation.org> <20230821-raven-abreibung-cc4abe44c9f5@brauner> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230821-raven-abreibung-cc4abe44c9f5@brauner> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, Aug 21, 2023 at 06:07:45PM +0200, Christian Brauner wrote: > > We will go to our plan b of having Willy drop the patch, resend the > > pull request to me .... > > No, I didn't drop it so I appreciate it if you went with your plan. > If I drop it now I'd be causing churn after having this sit in -next for > over 5 weeks and I'll send a pr in the middle of this week. I personally don't care about dropping it, but the whole process is unclear to me and I'm unsure about what I can/have to do if at all to help here. Thanks, Willy