From: Logan Gunthorpe <logang@deltatee.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-ntb@googlegroups.com, linux-crypto@vger.kernel.org,
Jyri Sarha <jsarha@ti.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Stephen Bates" <sbates@raithlin.com>,
"David Airlie" <airlied@linux.ie>
Subject: Re: [PATCH v6 1/7] drm/tilcdc: ensure nonatomic iowrite64 is not used
Date: Fri, 4 Aug 2017 09:47:37 -0600 [thread overview]
Message-ID: <15c19bbe-a178-5c60-530e-14229bfdc906@deltatee.com> (raw)
In-Reply-To: <2b41b02c-07e3-b927-f276-a29480f94285@ti.com>
On 04/08/17 07:03 AM, Tomi Valkeinen wrote:
> I haven't really followed the discussion on this, but if the tilcdc's
> use of iowrite64 causes (real) problems/complications elsewhere, I think
> we could drop it.
Well, that's up to you. The patch I submitted should still be correct
though, and if arm ever gets a proper atomic iowrite64 implementation it
would be good to use it. So in an annotative sense it's nice to keep the
function call in there.
Thanks,
Logan
next prev parent reply other threads:[~2017-08-04 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 18:30 [PATCH v6 0/7] make io{read|write}64 globally usable Logan Gunthorpe
2017-08-03 18:30 ` Logan Gunthorpe
2017-08-03 18:30 ` [PATCH v6 1/7] drm/tilcdc: ensure nonatomic iowrite64 is not used Logan Gunthorpe
2017-08-03 18:30 ` Logan Gunthorpe
2017-08-04 13:03 ` Tomi Valkeinen
2017-08-04 15:47 ` Logan Gunthorpe [this message]
2017-08-05 13:30 ` Jyri Sarha
2017-08-03 18:30 ` [PATCH v6 2/7] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs Logan Gunthorpe
2017-08-03 18:30 ` Logan Gunthorpe
2017-08-03 18:30 ` [PATCH v6 3/7] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe
2017-08-03 18:30 ` Logan Gunthorpe
2017-08-03 18:30 ` [PATCH v6 4/7] iomap: " Logan Gunthorpe
2017-08-03 18:30 ` Logan Gunthorpe
2017-08-03 18:30 ` [PATCH v6 5/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros Logan Gunthorpe
2017-08-03 18:30 ` Logan Gunthorpe
2017-08-03 18:30 ` [PATCH v6 6/7] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Logan Gunthorpe
2017-08-03 18:30 ` Logan Gunthorpe
2017-08-03 18:30 ` [PATCH v6 7/7] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Logan Gunthorpe
2017-08-03 18:30 ` Logan Gunthorpe
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=15c19bbe-a178-5c60-530e-14229bfdc906@deltatee.com \
--to=logang@deltatee.com \
--cc=airlied@linux.ie \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=horia.geanta@nxp.com \
--cc=jsarha@ti.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=sbates@raithlin.com \
--cc=tomi.valkeinen@ti.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