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 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_MUTT 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 8121FC282E1 for ; Fri, 24 May 2019 16:53:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 563AE217D7 for ; Fri, 24 May 2019 16:53:05 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="V2c3cbyo" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391049AbfEXQxE (ORCPT ); Fri, 24 May 2019 12:53:04 -0400 Received: from mail-vk1-f195.google.com ([209.85.221.195]:36773 "EHLO mail-vk1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390346AbfEXQxE (ORCPT ); Fri, 24 May 2019 12:53:04 -0400 Received: by mail-vk1-f195.google.com with SMTP id l199so2325814vke.3 for ; Fri, 24 May 2019 09:53:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=BWxqjKZCed63tdrqv52w7wsfWcnck29Bguoecq4JyuE=; b=V2c3cbyoJqcZX30pcTkJEv7QnnWfFOVUG/SZKLtnQEgMJVwm89vkCiLejgP7M+iRpN q/gLFJwalceC5ic9vkHhbkH+U/d7dt/5gsWtZqSmPEamXKr1uoECt4WeGoJqd2HwGhbx 9Occ1equYYbcXlCB88viJlGsBFmUVprPlSaUrUnpgJaFB5VgTgvCVd56gO+SEN+aAAgm xm1VbLsF+wb2n+Ta5LcBu1FilJNm/nl1Mj5onw2ziQywv/g3tjrYI+IB0DZ9YrwYdgB0 VEIEcUTbHmI4X7mxwSOIeASg6iishBSuXQpcZN/RP20qWAgLsgkprlD05w//8ySkAW73 D/4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=BWxqjKZCed63tdrqv52w7wsfWcnck29Bguoecq4JyuE=; b=q/gDiCnJQsmzJD4NF6kZN4l1ZmYWPImWCRcFXF1CBI8Rg+AHiJ+6nwwEHzt1Z7QBvA 266AZQimbyilLJ0XZ444mIlgnpRfvyFEQuuUKKIx1PCF2C36QHRcPE/n+qmNVhi9wyT2 jLE9WUSI2ld5LOKtaK1YUvIXy/guIW8bis5R15c2l7a4dvqFM6bVUu2DryOhtASCqKFt o9UFTVTzbvvlNnX/Sr+G5IgT8A6cSskBatQzNk59a+U+2AYGf/hbC7HxF05uUiscovnr kw3p8/sS0BeCW7kkPehT7egmSqaBq4lxO/PXb1vfOF/uExrKrtxCLCFO1FDrZc9/Hd28 kIDw== X-Gm-Message-State: APjAAAXA8cxXiglKvfPNclVHqMSDeqc1lEDfU+T7MS7PUA0FmW9Igz/W HnpTUZEBR4sTWVGukI8TNp3HSw== X-Google-Smtp-Source: APXvYqxGf4YX6m1bc63rX3ITovS0x9J+uBVKSme0zDKMj1gtik5rsITucqSrT8VXY0G62c80cqSI9A== X-Received: by 2002:a1f:fe81:: with SMTP id l123mr6286152vki.51.1558716782783; Fri, 24 May 2019 09:53:02 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-156-34-49-251.dhcp-dynamic.fibreop.ns.bellaliant.net. [156.34.49.251]) by smtp.gmail.com with ESMTPSA id b2sm1470363vkf.16.2019.05.24.09.53.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 24 May 2019 09:53:01 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1hUDRF-0008FA-F4; Fri, 24 May 2019 13:53:01 -0300 Date: Fri, 24 May 2019 13:53:01 -0300 From: Jason Gunthorpe To: Christoph Hellwig , akpm@linux-foundation.org, Dave Airlie , Linus Torvalds , Jerome Glisse , linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org, Leon Romanovsky , Doug Ledford , Artemy Kovalyov , Moni Shoua , Mike Marciniszyn , Kaike Wan , Dennis Dalessandro , linux-mm@kvack.org, dri-devel Subject: Re: RFC: Run a dedicated hmm.git for 5.3 Message-ID: <20190524165301.GD16845@ziepe.ca> References: <20190523154149.GB12159@ziepe.ca> <20190523155207.GC5104@redhat.com> <20190523163429.GC12159@ziepe.ca> <20190523173302.GD5104@redhat.com> <20190523175546.GE12159@ziepe.ca> <20190523182458.GA3571@redhat.com> <20190523191038.GG12159@ziepe.ca> <20190524064051.GA28855@infradead.org> <20190524124455.GB16845@ziepe.ca> <20190524162709.GD21222@phenom.ffwll.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190524162709.GD21222@phenom.ffwll.local> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 24, 2019 at 06:27:09PM +0200, Daniel Vetter wrote: > Sure topic branch sounds fine, we do that all the time with various > subsystems all over. We have ready made scripts for topic branches and > applying pulls from all over, so we can even soak test everything in our > integration tree. In case there's conflicts or just to make sure > everything works, before we bake the topic branch into permanent history > (the main drm.git repo just can't be rebased, too much going on and too > many people involvd). We don't rebase rdma.git either for the same reasons and nor does netdev So the usual flow for a shared topic branch is also no-rebase - testing/etc needs to be done before things get applied to it. Cheers, Jason