All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <ben.dooks@codethink.co.uk>, <palmer@dabbelt.com>
Cc: <linux-kernel@lists.codethink.co.uk>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] [PATCH v2] riscv: add as-options for modules with assembly compontents
Date: Mon, 25 Jul 2022 11:42:58 +0000	[thread overview]
Message-ID: <4768573b-80d6-b0a3-6430-064111d12cc7@microchip.com> (raw)
In-Reply-To: <15612a9b-004a-3bdf-cd3a-ec205a152e57@codethink.co.uk>

On 25/07/2022 12:38, Ben Dooks wrote:
> On 21/07/2022 20:53, Palmer Dabbelt wrote:
>> On Sun, 29 May 2022 08:22:00 PDT (-0700), ben.dooks@codethink.co.uk wrote:
> 
> [nip
> 
>>>  # GCC versions that support the "-mstrict-align" option default to allowing
>>>  # unaligned accesses.  While unaligned accesses are explicitly allowed in the
>>
>> Sorry for being so slow here, I've gotten pretty buried and it wasn't clear this was a fix.  I put it in fixes with some tags.
> 
> Is it time for linux-riscv list to have a patch tracker on? This might
> help with tracking patches for everyone.

https://patchwork.kernel.org/project/linux-riscv/list/

Just isn't used at all from what I can see.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2022-07-25 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 15:22 Ben Dooks
2022-05-29 15:22 ` Ben Dooks
2022-07-21 19:53 ` Palmer Dabbelt
2022-07-21 19:53   ` Palmer Dabbelt
2022-07-25 11:38   ` Ben Dooks
2022-07-25 11:42     ` Conor.Dooley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-20 14:44 Ben Dooks
2021-07-20 14:44 ` Ben Dooks
2021-08-10  8:49 ` Ben Dooks
2021-08-10  8:49   ` Ben Dooks

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=4768573b-80d6-b0a3-6430-064111d12cc7@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=ben.dooks@codethink.co.uk \
    --cc=linux-kernel@lists.codethink.co.uk \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --subject='Re: [PATCH] [PATCH v2] riscv: add as-options for modules with assembly compontents' \
    /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

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.