linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: Palmer Dabbelt <palmer@rivosinc.com>, corbet@lwn.net
Cc: linux@rivosinc.com, Paul Walmsley <paul.walmsley@sifive.com>,
	linux-doc@vger.kernel.org, bagasdotme@gmail.com,
	linux-kernel@vger.kernel.org, aou@eecs.berkeley.edu,
	Palmer Dabbelt <palmer@dabbelt.com>,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH] doc: RISC-V: Document that misaligned accesses are supported
Date: Wed, 12 Oct 2022 08:59:24 -0700	[thread overview]
Message-ID: <166559036448.27925.6190896060696605736.b4-ty@rivosinc.com> (raw)
In-Reply-To: <20220728210715.17214-1-palmer@rivosinc.com>

On Thu, 28 Jul 2022 14:07:15 -0700, Palmer Dabbelt wrote:
> From: Palmer Dabbelt <palmer@rivosinc.com>
> 
> The RISC-V ISA manual used to mandate that misaligned accesses were
> supported in user mode, but that requirement was removed in 2018 via
> riscv-isa-manual commit 61cadb9 ("Provide new description of misaligned
> load/store behavior compatible with privileged architecture.").  Since
> the Linux uABI was already frozen at that point it's just been demoted
> to part of the uABI, but that was never written down.
> 
> [...]

Applied, thanks!

[1/1] doc: RISC-V: Document that misaligned accesses are supported
      commit: 06267eb2decaa6baac81bbd882265a8e7782dba4

Best regards,
-- 
Palmer Dabbelt <palmer@rivosinc.com>

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

      reply	other threads:[~2022-10-12 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 21:07 [PATCH] doc: RISC-V: Document that misaligned accesses are supported Palmer Dabbelt
2022-10-12 15:59 ` Palmer Dabbelt [this message]

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=166559036448.27925.6190896060696605736.b4-ty@rivosinc.com \
    --to=palmer@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@rivosinc.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).