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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 30A1EC12002 for ; Wed, 21 Jul 2021 11:39:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 186B261001 for ; Wed, 21 Jul 2021 11:39:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237999AbhGUK6p (ORCPT ); Wed, 21 Jul 2021 06:58:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41394 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237982AbhGUKnA (ORCPT ); Wed, 21 Jul 2021 06:43:00 -0400 Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 80BD0C061762 for ; Wed, 21 Jul 2021 04:23:37 -0700 (PDT) Received: by mail-wr1-x436.google.com with SMTP id l7so1781957wrv.7 for ; Wed, 21 Jul 2021 04:23:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=5r4SARj9UXSpcoZXx50eoUO8FuzdCp7+FLIK6b9NrWI=; b=Cg//U4Y/1gDgxt7k5xmPgDyo0T0uwh0g+60Sh5AVkHS8/ei3NhtyBF6YUUZECQJ58p cUzo7OyBMRL1w7ZINYSSzxOiPjjdfCP8gmgVRIQrnKhlqKVsz4YOjpHWokj0QfreyYfD rHb7sejYFAOJAr8kwsiMNxNWVcph5CirgTBgM= 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:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=5r4SARj9UXSpcoZXx50eoUO8FuzdCp7+FLIK6b9NrWI=; b=aGYCdhOcN4cRYWJGWCR0LvyXbb5xj7CGLQOBJXsKwtFLXFhQOWuWIrTJ1yu90dX9f2 /CU/iq8x7cgIo9V7iJz7O5dUgcS3a83xI1qLeYd3WlMHS+AKZNoKcklgybRgp6/LTLw8 +KRd8CTNDEJdkB+squ2WFaKgrBofgyNC7i7EsdwM1aroUE2252U1C951a/+K3+Do8A+k gMAhRVGg/p1fOoQSzTZ+jpHkCB8R37iVL13pa+n+4SNuMlJjZt/SK2prw5rCRptlr5oJ jAeFO0zU9JssDft+qZbSgDeC4yiA8/9jI8vbB6Dgts8QSxLi8zg+J8Aufah2NIhlA2Ix hRqw== X-Gm-Message-State: AOAM531dL9YEpG8jm2Fmcw58bqI5QThDfarYOiDl8RlMY/JWCIdb7gmb BGIIsNbmpIXMPkxaaKDIHxWctQ== X-Google-Smtp-Source: ABdhPJz23x9YYT7kn6ADtNpcXFeq0lIiwVkk98kY+doYcdNtjlUQIlafrn5wFGkpRjXik49b18LU5g== X-Received: by 2002:a5d:6482:: with SMTP id o2mr41030703wri.367.1626866616114; Wed, 21 Jul 2021 04:23:36 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:57f4:0:efd0:b9e5:5ae6:c2fa]) by smtp.gmail.com with ESMTPSA id f26sm21862934wmc.29.2021.07.21.04.23.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Jul 2021 04:23:35 -0700 (PDT) Date: Wed, 21 Jul 2021 13:23:33 +0200 From: Daniel Vetter To: Javier Martinez Canillas Cc: Thomas Zimmermann , Ard Biesheuvel , Dave Airlie , linux-efi , David Airlie , Catalin Marinas , dri-devel , Russell King , Atish Patra , linux-riscv , Will Deacon , the arch/x86 maintainers , Ingo Molnar , Peter Robinson , Borislav Petkov , Albert Ou , Hans de Goede , Paul Walmsley , Thomas Gleixner , linux-arm-kernel , Greg Kroah-Hartman , LKML , Palmer Dabbelt Subject: Re: [PATCH v3 0/2] allow simple{fb, drm} drivers to be used on non-x86 EFI platforms Message-ID: Mail-Followup-To: Javier Martinez Canillas , Thomas Zimmermann , Ard Biesheuvel , Dave Airlie , linux-efi , David Airlie , Catalin Marinas , dri-devel , Russell King , Atish Patra , linux-riscv , Will Deacon , the arch/x86 maintainers , Ingo Molnar , Peter Robinson , Borislav Petkov , Albert Ou , Hans de Goede , Paul Walmsley , Thomas Gleixner , linux-arm-kernel , Greg Kroah-Hartman , LKML , Palmer Dabbelt References: <8dd26141-a09c-39e2-5174-4cad8d21c49c@suse.de> <03f0edef-e54e-8a2a-4b50-683d3d42e249@redhat.com> <37e05f02-b810-0cb1-cc4f-95711cd148d9@suse.de> <44a75f18-e3a6-f764-b0ec-ce3ac05805a9@redhat.com> <1e85fae7-ef95-b2f7-3463-e90958e54684@suse.de> <0ad257ce-44d9-beea-8afb-c879146c523b@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0ad257ce-44d9-beea-8afb-c879146c523b@redhat.com> X-Operating-System: Linux phenom 5.10.0-7-amd64 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 21, 2021 at 12:15:12PM +0200, Javier Martinez Canillas wrote: > On 7/21/21 12:07 PM, Thomas Zimmermann wrote: > > Hi > > > > Am 21.07.21 um 07:09 schrieb Javier Martinez Canillas: > > ... > >>> > >>> Can I simply put the patches in to drm-misc-next? There was some talk > >>> about a topic branch? > >>> > >> > >> ... which AFAIU means that there's no need for a topic branch, since the > >> patches will be present in linux-next. And the EFI folks can use that to > >> check if there are any integration issues or regressions caused by these. > > > > Merged into drm-misc-next. > > > > Thanks a lot Thomas for all your help! Yeah topic branch makes sense when we have further work that will build on top of a patch sets in at latest _two_ different subsystems, and it doesn't make sense to just merge it all in one place (because too much work, or a refactoring that's too invasive and will cause random conflicts with subsequent work in the same subsystem, or ...). Otherwise just acks and then merge in one place. We shouldn't do bureaucratics like topic branches if there's not an actual need for them. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch