All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Conor Dooley <conor@kernel.org>, Costa Shulyupin <costa.shul@redhat.com>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Federico Vaga" <federico.vaga@vaga.pv.it>,
	"Alex Shi" <alexs@kernel.org>,
	"Yanteng Si" <siyanteng@loongson.cn>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Atish Patra" <atishp@rivosinc.com>,
	"Alexandre Ghiti" <alexghiti@rivosinc.com>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Andrew Jones" <ajones@ventanamicro.com>,
	"Evan Green" <evan@rivosinc.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"Andy Chiu" <andy.chiu@sifive.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Greentime Hu" <greentime.hu@sifive.com>,
	"Anup Patel" <anup@brainfault.org>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Charlie Jenkins" <charlie@rivosinc.com>,
	"Vincent Chen" <vincent.chen@sifive.com>,
	"Wu XiangCheng" <bobwxc@email.cn>,
	"Sami Tolvanen" <samitolvanen@google.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, workflows@vger.kernel.org
Subject: Re: [PATCH] docs: move riscv under arch
Date: Sat, 30 Sep 2023 08:26:38 -0600	[thread overview]
Message-ID: <87h6nbka8x.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230930-mauve-jargon-0f7760fd262d@spud>

Conor Dooley <conor@kernel.org> writes:

> On Thu, Sep 28, 2023 at 01:29:42PM +0300, Costa Shulyupin wrote:
>> and fix all in-tree references.
>> 
>> Architecture-specific documentation is being moved into Documentation/arch/
>> as a way of cleaning up the top-level documentation directory and making
>> the docs hierarchy more closely match the source hierarchy.
>> 
>> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
>
> This doesn't apply to riscv/for-next or next/master, with git
> complaining about the sha1 being lacking or useless. What does this
> actually apply to?

docs-next, I would guess (though I haven't had a chance to try it).  If
you would like to carry this through the riscv tree (which is probably
the most sensible option), I suspect Costa could be talked into
respinning it...?

Thanks,

jon

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Conor Dooley <conor@kernel.org>, Costa Shulyupin <costa.shul@redhat.com>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Federico Vaga" <federico.vaga@vaga.pv.it>,
	"Alex Shi" <alexs@kernel.org>,
	"Yanteng Si" <siyanteng@loongson.cn>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Atish Patra" <atishp@rivosinc.com>,
	"Alexandre Ghiti" <alexghiti@rivosinc.com>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Andrew Jones" <ajones@ventanamicro.com>,
	"Evan Green" <evan@rivosinc.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"Andy Chiu" <andy.chiu@sifive.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Greentime Hu" <greentime.hu@sifive.com>,
	"Anup Patel" <anup@brainfault.org>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Charlie Jenkins" <charlie@rivosinc.com>,
	"Vincent Chen" <vincent.chen@sifive.com>,
	"Wu XiangCheng" <bobwxc@email.cn>,
	"Sami Tolvanen" <samitolvanen@google.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, workflows@vger.kernel.org
Subject: Re: [PATCH] docs: move riscv under arch
Date: Sat, 30 Sep 2023 08:26:38 -0600	[thread overview]
Message-ID: <87h6nbka8x.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230930-mauve-jargon-0f7760fd262d@spud>

Conor Dooley <conor@kernel.org> writes:

> On Thu, Sep 28, 2023 at 01:29:42PM +0300, Costa Shulyupin wrote:
>> and fix all in-tree references.
>> 
>> Architecture-specific documentation is being moved into Documentation/arch/
>> as a way of cleaning up the top-level documentation directory and making
>> the docs hierarchy more closely match the source hierarchy.
>> 
>> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
>
> This doesn't apply to riscv/for-next or next/master, with git
> complaining about the sha1 being lacking or useless. What does this
> actually apply to?

docs-next, I would guess (though I haven't had a chance to try it).  If
you would like to carry this through the riscv tree (which is probably
the most sensible option), I suspect Costa could be talked into
respinning it...?

Thanks,

jon

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-09-30 14:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 10:29 [PATCH] docs: move riscv under arch Costa Shulyupin
2023-09-28 10:29 ` Costa Shulyupin
2023-09-28 10:58 ` Bagas Sanjaya
2023-09-28 10:58   ` Bagas Sanjaya
2023-09-30  9:06 ` Conor Dooley
2023-09-30  9:06   ` Conor Dooley
2023-09-30 14:26   ` Jonathan Corbet [this message]
2023-09-30 14:26     ` Jonathan Corbet
2023-09-30 18:52     ` [PATCH v1] " Costa Shulyupin
2023-09-30 18:52       ` Costa Shulyupin
2023-10-02 13:25       ` Conor Dooley
2023-10-02 13:25         ` Conor Dooley
2023-10-10 19:47       ` Jonathan Corbet
2023-10-10 19:47         ` Jonathan Corbet
2023-11-12  0:55       ` patchwork-bot+linux-riscv
2023-11-12  0:55         ` patchwork-bot+linux-riscv
2023-10-02 13:15     ` [PATCH] " Conor Dooley
2023-10-02 13:15       ` Conor Dooley
2023-10-02 15:32       ` Jonathan Corbet
2023-10-02 15:32         ` Jonathan Corbet

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=87h6nbka8x.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=ajones@ventanamicro.com \
    --cc=alexghiti@rivosinc.com \
    --cc=alexs@kernel.org \
    --cc=andy.chiu@sifive.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=atishp@rivosinc.com \
    --cc=bagasdotme@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn@rivosinc.com \
    --cc=bobwxc@email.cn \
    --cc=charlie@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=costa.shul@redhat.com \
    --cc=evan@rivosinc.com \
    --cc=federico.vaga@vaga.pv.it \
    --cc=greentime.hu@sifive.com \
    --cc=hca@linux.ibm.com \
    --cc=heiko@sntech.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=philmd@linaro.org \
    --cc=rdunlap@infradead.org \
    --cc=samitolvanen@google.com \
    --cc=siyanteng@loongson.cn \
    --cc=vincent.chen@sifive.com \
    --cc=workflows@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.