All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	conor.dooley@microchip.com, linux-doc@vger.kernel.org,
	corbet@lwn.net, lkp@intel.com
Subject: Re: [PATCH] Documentation: riscv: fix insufficient list item indent
Date: Wed, 15 Feb 2023 15:00:20 +0000	[thread overview]
Message-ID: <167647322055.11521.14296165976216354601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230129235701.2393241-1-conor@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Sun, 29 Jan 2023 23:57:01 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> When adding the ISA string ordering rules, I didn't sufficiently indent
> one of the list items.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: f07b2b3f9d47 ("Documentation: riscv: add a section about ISA string ordering in /proc/cpuinfo")
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> 
> [...]

Here is the summary with links:
  - Documentation: riscv: fix insufficient list item indent
    https://git.kernel.org/riscv/c/2a5303b499b1

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



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	conor.dooley@microchip.com, linux-doc@vger.kernel.org,
	corbet@lwn.net, lkp@intel.com
Subject: Re: [PATCH] Documentation: riscv: fix insufficient list item indent
Date: Wed, 15 Feb 2023 15:00:20 +0000	[thread overview]
Message-ID: <167647322055.11521.14296165976216354601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230129235701.2393241-1-conor@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Sun, 29 Jan 2023 23:57:01 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> When adding the ISA string ordering rules, I didn't sufficiently indent
> one of the list items.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: f07b2b3f9d47 ("Documentation: riscv: add a section about ISA string ordering in /proc/cpuinfo")
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> 
> [...]

Here is the summary with links:
  - Documentation: riscv: fix insufficient list item indent
    https://git.kernel.org/riscv/c/2a5303b499b1

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



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

  parent reply	other threads:[~2023-02-15 15:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 23:57 [PATCH] Documentation: riscv: fix insufficient list item indent Conor Dooley
2023-01-29 23:57 ` Conor Dooley
2023-01-30  3:05 ` Bagas Sanjaya
2023-01-30  3:05   ` Bagas Sanjaya
2023-01-31 19:18   ` Conor Dooley
2023-01-31 19:18     ` Conor Dooley
2023-02-09 18:48   ` Palmer Dabbelt
2023-02-09 18:48     ` Palmer Dabbelt
2023-02-09 19:23     ` Conor Dooley
2023-02-09 19:23       ` Conor Dooley
2023-02-07 14:58 ` Conor Dooley
2023-02-07 14:58   ` Conor Dooley
2023-02-09 18:48   ` Palmer Dabbelt
2023-02-09 18:48     ` Palmer Dabbelt
2023-02-09 18:44 ` Palmer Dabbelt
2023-02-09 18:44   ` Palmer Dabbelt
2023-02-15 15:00 ` patchwork-bot+linux-riscv [this message]
2023-02-15 15:00   ` patchwork-bot+linux-riscv

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=167647322055.11521.14296165976216354601.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=palmer@dabbelt.com \
    /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.