workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Costa Shulyupin <costa.shul@redhat.com>
Cc: linux-riscv@lists.infradead.org, corbet@lwn.net,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, federico.vaga@vaga.pv.it,
	alexs@kernel.org, siyanteng@loongson.cn, philmd@linaro.org,
	hca@linux.ibm.com, ardb@kernel.org, atishp@rivosinc.com,
	alexghiti@rivosinc.com, sunilvl@ventanamicro.com,
	evan@rivosinc.com, conor.dooley@microchip.com, heiko@sntech.de,
	andy.chiu@sifive.com, bhelgaas@google.com,
	songshuaishuai@tinylab.org, ajones@ventanamicro.com,
	bjorn@rivosinc.com, anup@brainfault.org, bagasdotme@gmail.com,
	charlie@rivosinc.com, catalin.marinas@arm.com, bobwxc@email.cn,
	samitolvanen@google.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH v1] docs: move riscv under arch
Date: Sun, 12 Nov 2023 00:55:46 +0000	[thread overview]
Message-ID: <169975054646.11360.7774579809979814716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230930185354.3034118-1-costa.shul@redhat.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Jonathan Corbet <corbet@lwn.net>:

On Sat, 30 Sep 2023 21:52:00 +0300 you 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>
> 
> [...]

Here is the summary with links:
  - [v1] docs: move riscv under arch
    https://git.kernel.org/riscv/c/ed843ae947f8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-11-12  0:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 10:29 [PATCH] " Costa Shulyupin
2023-09-28 10:58 ` Bagas Sanjaya
2023-09-30  9:06 ` Conor Dooley
2023-09-30 14:26   ` Jonathan Corbet
2023-09-30 18:52     ` [PATCH v1] " Costa Shulyupin
2023-10-02 13:25       ` Conor Dooley
2023-10-10 19:47       ` Jonathan Corbet
2023-11-12  0:55       ` patchwork-bot+linux-riscv [this message]
2023-10-02 13:15     ` [PATCH] " Conor Dooley
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=169975054646.11360.7774579809979814716.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --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=catalin.marinas@arm.com \
    --cc=charlie@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=corbet@lwn.net \
    --cc=costa.shul@redhat.com \
    --cc=evan@rivosinc.com \
    --cc=federico.vaga@vaga.pv.it \
    --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=samitolvanen@google.com \
    --cc=siyanteng@loongson.cn \
    --cc=songshuaishuai@tinylab.org \
    --cc=sunilvl@ventanamicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox