public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the pci tree
Date: Tue, 1 Mar 2022 09:01:36 -0600	[thread overview]
Message-ID: <20220301150136.GA609359@bhelgaas> (raw)
In-Reply-To: <20220301135938.4c664beb@canb.auug.org.au>

On Tue, Mar 01, 2022 at 01:59:38PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the pci tree, today's linux-next build (htmldocs) produced
> these warnings:
> 
> Error: Cannot open file drivers/gpu/vga/vgaarb.c
> Error: Cannot open file drivers/gpu/vga/vgaarb.c
> 
> Introduced by commit
> 
>   d6e1898bfa5b ("PCI/VGA: Move vgaarb to drivers/pci")
> 
> The reference in Documentation/gpu/vgaarbiter.rst needs to be updated.

Fixed, thanks!

  reply	other threads:[~2022-03-01 15:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  2:59 linux-next: build warnings after merge of the pci tree Stephen Rothwell
2022-03-01 15:01 ` Bjorn Helgaas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-05  5:00 Stephen Rothwell
2024-02-05  5:09 Stephen Rothwell
2024-02-06 20:21 ` Philipp Stanner
2018-10-02  0:26 Stephen Rothwell
2018-10-02 13:47 ` Bjorn Helgaas
2016-06-20  1:52 Stephen Rothwell
2016-06-20 19:11 ` Bjorn Helgaas
2016-06-21  1:08   ` Stephen Rothwell
2016-06-21  1:27     ` Bjorn Helgaas
     [not found] <EDA0A4495861324DA2618B4C45DCB3EE612CE1@blrx3m08.blr.amer.dell.com>
2010-08-02 12:44 ` Narendra K
2010-08-02  1:18 Stephen Rothwell
2010-08-02  1:38 ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220301150136.GA609359@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox