Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp2330435ybd; Thu, 27 Jun 2019 10:32:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqxtxKv99c0ibPeSQA+puRkS/XgUBASd8HtjfhPOyhJIVQRW/acMWyDE/3LlBDUlqOWQks3d X-Received: by 2002:a63:b22:: with SMTP id 34mr2030727pgl.38.1561656766253; Thu, 27 Jun 2019 10:32:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561656766; cv=none; d=google.com; s=arc-20160816; b=pBUPgTkrEpFJFd8p3HWV5WZTUIev3ZvKy6fLvi5aE5oAWtvVjJ56g5Sj16qpLEl8M2 OBfQLwCU793vn/fBuwGdTZD6pnQDyLD5F8toeO1htCEPlT/cmg2O7x7OXxvuJfQIgaUP OQOf9YwFgXeNjq0kE47nRkErp3ZJYqvETO0pLPs4h7rZz1hZb1CmCfRxAPOCNCQO1sip I4WCzluSU/MLoapEHqPRE2h/irF/rnQ39IbvUPSLf4Ui46bd3K4r5g3paYKKdLijE0/w SreU6/TPvwl+VapAKXYg7yHJSYW84PySIRkeMu/DaLKbOdP2uh4F8fYAT9yEqHHLTS4w +oFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=ExPXpO5gTITc0uk76yr/ill6Vu0qlltHQ2s6JQWtlmE=; b=xnkW3/lwvaJ68vUWepXPNzHvW96TZpd1Xacced1jQRg7IPl47nnhbci9dE9V57nkFF VoxFM/bSvVlI/5Q4YYWbry4MRSFrLvipPqoBYkoIjz3U8N2CKXnxnbeTpQO6xvdbMBcu G6c1E9aM83uwG9y0XGc54gaDV1XmHRczrPT3F0POGwqaWcKVX8BYLMjUlFH9OJhm/CXd soCZudJgHEcVdgmPlPWo6olth4/2/F2PSZ7pOi3m2yRO4TthC28Yjugco+EVemzrC0sb ovnoIuUo9YhU7mSQbbhsDIoq5u/mzTVvyDUe7BvUPdCti0nsa3F57SG9flipe8co4DDu tuCA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d128si159100pfd.160.2019.06.27.10.32.30; Thu, 27 Jun 2019 10:32:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726622AbfF0RbZ (ORCPT + 99 others); Thu, 27 Jun 2019 13:31:25 -0400 Received: from ms.lwn.net ([45.79.88.28]:56912 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726540AbfF0RbY (ORCPT ); Thu, 27 Jun 2019 13:31:24 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id F0B2C537; Thu, 27 Jun 2019 17:31:23 +0000 (UTC) Date: Thu, 27 Jun 2019 11:31:22 -0600 From: Jonathan Corbet To: Daniel Vetter Cc: Mauro Carvalho Chehab , Linux Doc Mailing List , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Maarten Lankhorst , Maxime Ripard , Sean Paul , David Airlie , dri-devel@lists.freedesktop.org Subject: Re: [PATCH] drm: fix a reference for a renamed file: fb/modedb.rst Message-ID: <20190627113122.34b46ee2@lwn.net> In-Reply-To: <20190626212735.GY12905@phenom.ffwll.local> References: <699d7618720e2808f9aa094a13ab2f3545c3c25c.1561565652.git.mchehab+samsung@kernel.org> <20190626212735.GY12905@phenom.ffwll.local> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Jun 2019 23:27:35 +0200 Daniel Vetter wrote: > On Wed, Jun 26, 2019 at 01:14:13PM -0300, Mauro Carvalho Chehab wrote: > > Due to two patches being applied about the same time, the > > reference for modedb.rst file got wrong: > > > > Documentation/fb/modedb.txt is now Documentation/fb/modedb.rst. > > > > Fixes: 1bf4e09227c3 ("drm/modes: Allow to specify rotation and reflection on the commandline") > > Fixes: ab42b818954c ("docs: fb: convert docs to ReST and rename to *.rst") > > Signed-off-by: Mauro Carvalho Chehab > > What's the merge plan here? doc-next? If so: > > Acked-by: Daniel Vetter It doesn't really apply to docs-next, so that's probably not the best path unless I hold it until after the merge window. Seems like it needs to go through the DRM tree to me. Thanks, jon