From: "Michael T. Kloos" <michael@michaelkloos.com>
To: David Laight <David.Laight@ACULAB.COM>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>
Cc: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Fixed: Misaligned memory access. Fixed pointer comparison.
Date: Sun, 23 Jan 2022 18:03:07 -0500 [thread overview]
Message-ID: <5dca7098-0986-1e2a-1452-124c506b1241@michaelkloos.com> (raw)
In-Reply-To: <228cbdb42a5c4c2f9d7214d2685fcaeb@AcuMS.aculab.com>
No problem. If you have any other concerns about my patch, please let me know.
Michael
On 1/23/22 17:35, David Laight wrote:
> From: michael@michaelkloos.com
>> Sent: 23 January 2022 16:54
>>
>> No. It only uses tabs. The previous version used spaces.
> Ah, it was the old one that was wrong.
> One of them was.
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
WARNING: multiple messages have this Message-ID (diff)
From: "Michael T. Kloos" <michael@michaelkloos.com>
To: David Laight <David.Laight@ACULAB.COM>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>
Cc: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Fixed: Misaligned memory access. Fixed pointer comparison.
Date: Sun, 23 Jan 2022 18:03:07 -0500 [thread overview]
Message-ID: <5dca7098-0986-1e2a-1452-124c506b1241@michaelkloos.com> (raw)
In-Reply-To: <228cbdb42a5c4c2f9d7214d2685fcaeb@AcuMS.aculab.com>
No problem. If you have any other concerns about my patch, please let me know.
Michael
On 1/23/22 17:35, David Laight wrote:
> From: michael@michaelkloos.com
>> Sent: 23 January 2022 16:54
>>
>> No. It only uses tabs. The previous version used spaces.
> Ah, it was the old one that was wrong.
> One of them was.
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-01-23 23:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 3:45 [PATCH v2] Fixed: Misaligned memory access. Fixed pointer comparison Michael T. Kloos
2022-01-23 3:45 ` Michael T. Kloos
2022-01-23 13:31 ` David Laight
2022-01-23 13:31 ` David Laight
2022-01-23 16:53 ` Michael T. Kloos
2022-01-23 16:53 ` Michael T. Kloos
2022-01-23 22:35 ` David Laight
2022-01-23 22:35 ` David Laight
2022-01-23 23:03 ` Michael T. Kloos [this message]
2022-01-23 23:03 ` Michael T. Kloos
2022-01-23 15:44 ` Jessica Clarke
2022-01-23 15:44 ` Jessica Clarke
2022-01-23 17:15 ` Michael T. Kloos
2022-01-23 17:15 ` Michael T. Kloos
2022-01-24 9:21 ` David Laight
2022-01-24 9:21 ` David Laight
2022-01-24 19:19 ` Michael T. Kloos
2022-01-24 19:19 ` Michael T. Kloos
2022-01-24 22:28 ` David Laight
2022-01-24 22:28 ` David Laight
2022-01-24 13:38 ` kernel test robot
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=5dca7098-0986-1e2a-1452-124c506b1241@michaelkloos.com \
--to=michael@michaelkloos.com \
--cc=David.Laight@ACULAB.COM \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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 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.