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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (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 8E6B8EB64DC for ; Thu, 29 Jun 2023 15:54:53 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 6707610E3EC; Thu, 29 Jun 2023 15:54:43 +0000 (UTC) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by gabe.freedesktop.org (Postfix) with ESMTPS id C70A310E3E2; Thu, 29 Jun 2023 15:54:40 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 54A82614DC; Thu, 29 Jun 2023 15:54:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 28680C433C8; Thu, 29 Jun 2023 15:54:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1688054078; bh=L6FQS4d7vn+9QEms0SfAm1VLkLjV+bIazDI0tjMBu5g=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=k8QvCfS9YYp1B+ART94SdyS5GCq+kzg+y0GcPPcxH+Mz9b1I4fFjWlHyii0LCx/Zb 6oqHcWtiuE3GTIm5ZtGtpI5GJoj+Uki8akhd/tLN8XIvFLJ4vCNRMSzWFjh3vcU96P F6nnnWDIE4ZC6jcq+iQOB7KR1kmI5HAuZgfRETPIGLrJefP/K7dQk2FX6jv6Do9o62 6dFS9sWsPtWknyZX4osw36zBl8rdJv7ce0BtqwOjDubXmJlfxwaLWPMCaZA0PiKewB /QBRqLcnYPOwgUGemUscA0GTUkIR0SFl9qk65pBR8RcIQJ0ANd+rxatzb7VXpj8G2x dcnTEBewzlWmg== Date: Thu, 29 Jun 2023 10:54:36 -0500 From: Bjorn Helgaas To: Sui Jingfeng Message-ID: <20230629155436.GA397963@bhelgaas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0dd961ae-78a7-0b67-af51-008ecbcdbbef@loongson.cn> Subject: Re: [Intel-gfx] [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-fbdev@vger.kernel.org, Pan Xinhui , kvm@vger.kernel.org, nouveau@lists.freedesktop.org, Lijo Lazar , dri-devel@lists.freedesktop.org, YiPeng Chai , Mario Limonciello , Likun Gao , David Airlie , Yi Liu , Karol Herbst , amd-gfx@lists.freedesktop.org, Sui Jingfeng <15330273260@189.cn>, Jason Gunthorpe , Ben Skeggs , linux-pci@vger.kernel.org, Kevin Tian , Daniel Vetter , Bokun Zhang , intel-gfx@lists.freedesktop.org, Abhishek Sahu , Maxime Ripard , Rodrigo Vivi , Bjorn Helgaas , Yishai Hadas , Cornelia Huck , linux-kernel@vger.kernel.org, Thomas Zimmermann , Alex Deucher , Christian Konig , Hawking Zhang Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Thu, Jun 22, 2023 at 01:08:15PM +0800, Sui Jingfeng wrote: > Hi, > > > A nouveau developer(Lyude) from redhat send me a R-B, > > Thanks for the developers of nouveau project. > > > Please allow me add a link[1] here. > > > [1] https://lore.kernel.org/all/0afadc69f99a36bc9d03ecf54ff25859dbc10e28.camel@redhat.com/ 1) Thanks for this. If you post another version of this series, please pick up Lyude's Reviewed-by and include it in the relevant patches (as long as you haven't made significant changes to the code Lyude reviewed). Whoever applies this should automatically pick up Reviewed-by/Ack/etc that are replies to the version being applied, but they won't go through previous revisions to find them. 2) Please mention the commit to which the series applies. I tried to apply this on v6.4-rc1, but it doesn't apply cleanly. 3) Thanks for including cover letters in your postings. Please include a little changelog in the cover letter so we know what changed between v6 and v7, etc. 4) Right now we're in the middle of the v6.5 merge window, so new content, e.g., this series, is too late for v6.5. Most maintainers, including me, wait to merge new content until the merge window closes and a new -rc1 is tagged. This merge window should close on July 9, and people will start merging content for v6.6, typically based on v6.5-rc1. Bjorn