From: Conor Dooley <conor@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: palmer@dabbelt.com, Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, linux-doc@vger.kernel.org,
corbet@lwn.net, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] Documentation: riscv: fix insufficient list item indent
Date: Tue, 31 Jan 2023 19:18:01 +0000 [thread overview]
Message-ID: <Y9lpaRqUEB2YbLyG@spud> (raw)
In-Reply-To: <Y9c0EU5epWCeoPB8@debian.me>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Mon, Jan 30, 2023 at 10:05:53AM +0700, Bagas Sanjaya wrote:
> On Sun, Jan 29, 2023 at 11:57:01PM +0000, Conor Dooley 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>
>
> Seems like you forget to add link to the report:
>
> Link: https://lore.kernel.org/linux-doc/202301300743.bp7Dpazv-lkp@intel.com/
No, I didn't forget actually. I just didn't think it added any useful
information. No harm having it though I suppose, but I'll not resend to
add it.
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: palmer@dabbelt.com, Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, linux-doc@vger.kernel.org,
corbet@lwn.net, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] Documentation: riscv: fix insufficient list item indent
Date: Tue, 31 Jan 2023 19:18:01 +0000 [thread overview]
Message-ID: <Y9lpaRqUEB2YbLyG@spud> (raw)
In-Reply-To: <Y9c0EU5epWCeoPB8@debian.me>
[-- Attachment #1.1: Type: text/plain, Size: 837 bytes --]
On Mon, Jan 30, 2023 at 10:05:53AM +0700, Bagas Sanjaya wrote:
> On Sun, Jan 29, 2023 at 11:57:01PM +0000, Conor Dooley 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>
>
> Seems like you forget to add link to the report:
>
> Link: https://lore.kernel.org/linux-doc/202301300743.bp7Dpazv-lkp@intel.com/
No, I didn't forget actually. I just didn't think it added any useful
information. No harm having it though I suppose, but I'll not resend to
add it.
Thanks,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-01-31 19:18 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 [this message]
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
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=Y9lpaRqUEB2YbLyG@spud \
--to=conor@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=conor.dooley@microchip.com \
--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.