From: Greg Ungerer <gregungerer00@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Angelo Dureghello <angelo@sysam.it>,
Logan Gunthorpe <logang@deltatee.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] m68k: io: Fix io{read,write}{16,32}be() for Coldfire peripherals
Date: Wed, 5 Jun 2019 22:52:51 +1000 [thread overview]
Message-ID: <f5e30b21-3c88-c134-d2bb-dabd191c6122@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdVTOO13Y49D82r5YgTFGwvgB0UdCZ3o1VAXHWzYof05xA@mail.gmail.com>
Hi Geert,
On 4/6/19 5:34 pm, Geert Uytterhoeven wrote:
> On Tue, Jun 4, 2019 at 9:18 AM Greg Ungerer <gerg@linux-m68k.org> wrote:
>> On 3/6/19 10:26 pm, Angelo Dureghello wrote:
>>> couldn't seen any follow up on this patch. I tested it and at least
>>> for mcf5441x it works properly and solves all issues.
>>>
>>> Do you think it may be accepted as an initial fix ?
>>
>> I'll add it to the m68knommu git tree.
>> Seeing as you wrote it Geert I assume you have no problem with that? :-)
>
> Actually I wanted to look into the issues pointed out by Arnd, but didn't
> get to that yet...
Ok, no worries. I won't do anything with this right now then.
Regards
Greg
prev parent reply other threads:[~2019-06-05 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 8:19 Geert Uytterhoeven
2019-04-29 12:39 ` Arnd Bergmann
2019-05-11 10:55 ` Angelo Dureghello
2019-06-14 14:49 ` Geert Uytterhoeven
2019-06-17 20:23 ` Arnd Bergmann
2019-06-03 12:26 ` Angelo Dureghello
2019-06-04 7:18 ` Greg Ungerer
2019-06-04 7:34 ` Geert Uytterhoeven
2019-06-05 12:52 ` Greg Ungerer [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=f5e30b21-3c88-c134-d2bb-dabd191c6122@linux-m68k.org \
--to=gregungerer00@gmail.com \
--cc=angelo@sysam.it \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=logang@deltatee.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
all inboxes | Powered by JetHome®