From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ozgur Kara <ozgur@goosey•org>
Cc: Jonathan Corbet <corbet@lwn•net>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge all the trees
Date: Thu, 8 May 2025 19:27:13 +1000 [thread overview]
Message-ID: <20250508192713.4fd440e4@canb.auug.org.au> (raw)
In-Reply-To: <01100196af3237f3-279dac0b-ad07-4f5c-bbd7-0e0f2d14659a-000000@eu-north-1.amazonses.com>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
Hi Ozgur,
On Thu, 8 May 2025 09:20:26 +0000 Ozgur Kara <ozgur@goosey•org> wrote:
>
> Did you run this command before you got this error?
>
> $ make htmldocs
>
> but the error shows itself because index.rst is not in need requested
> directory, please run:
>
> $ git restore Documentation/index.rst
>
> Can this solve it?
Please see my second email.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-08 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 8:25 linux-next: build failure after merge all the trees Stephen Rothwell
2025-05-08 8:48 ` Stephen Rothwell
2025-05-08 10:54 ` Akira Yokosawa
2025-05-08 12:25 ` Stephen Rothwell
2025-05-08 12:39 ` Mauro Carvalho Chehab
2025-05-15 2:33 ` Akira Yokosawa
2025-05-19 19:33 ` Randy Dunlap
2025-05-20 5:18 ` Mauro Carvalho Chehab
2025-05-20 5:55 ` Mauro Carvalho Chehab
2025-05-09 0:46 ` Dan Williams
2025-05-09 6:47 ` Mauro Carvalho Chehab
2025-05-08 9:20 ` Ozgur Kara
[not found] ` <01100196af3237f3-279dac0b-ad07-4f5c-bbd7-0e0f2d14659a-000000@eu-north-1.amazonses.com>
2025-05-08 9:27 ` Stephen Rothwell [this message]
2025-05-08 9:35 ` Ozgur Kara
2025-05-08 12:23 ` Mauro Carvalho Chehab
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=20250508192713.4fd440e4@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ozgur@goosey$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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