From: Fabio Estevam <festevam@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Geert Uytterhoeven <geert@linux-m68k.org>,
paulus@samba.org, Mauro Carvalho Chehab <mchehab@kernel.org>,
linuxppc-dev@lists.ozlabs.org,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] media: fsl-viu: Use proper check for presence of {out, in}_be32()
Date: Fri, 20 Nov 2020 10:31:11 -0300 [thread overview]
Message-ID: <CAOMZO5CrtC627GJ=fM6Wruf765pfxAGboPJhfDrhYG5a2OjpRA@mail.gmail.com> (raw)
In-Reply-To: <87ima01r52.fsf@mpe.ellerman.id.au>
Hi Michael,
On Fri, Nov 20, 2020 at 3:25 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
> I'd rather not have to carry this in arch code just for one driver.
Fair enough.
> Can't the driver just use ioread/write32be() on all platforms?
Yes, this is a better approach. I have just a patch doing that.
Thanks
next prev parent reply other threads:[~2020-11-20 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 0:15 [PATCH] media: fsl-viu: Use proper check for presence of {out, in}_be32() Fabio Estevam
2020-11-20 6:25 ` Michael Ellerman
2020-11-20 13:31 ` Fabio Estevam [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-19 8:01 Geert Uytterhoeven
2018-06-08 9:48 Geert Uytterhoeven
2018-06-15 8:10 ` [PATCH] media: fsl-viu: Use proper check for presence of {out,in}_be32() Hans Verkuil
2019-01-18 10:07 ` Hans Verkuil
2019-01-18 10:45 ` [PATCH] media: fsl-viu: Use proper check for presence of {out, in}_be32() Geert Uytterhoeven
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='CAOMZO5CrtC627GJ=fM6Wruf765pfxAGboPJhfDrhYG5a2OjpRA@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mchehab@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).