From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Corbet Subject: Re: [PATCH] drm: fix a reference for a renamed file: fb/modedb.rst Date: Thu, 27 Jun 2019 11:31:22 -0600 Message-ID: <20190627113122.34b46ee2@lwn.net> References: <699d7618720e2808f9aa094a13ab2f3545c3c25c.1561565652.git.mchehab+samsung@kernel.org> <20190626212735.GY12905@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <20190626212735.GY12905@phenom.ffwll.local> Sender: linux-kernel-owner@vger.kernel.org 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 List-Id: dri-devel@lists.freedesktop.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