From: Arnd Bergmann <arnd@arndb.de>
To: kbuild test robot <lkp@intel.com>
Cc: Nava kishore Manne <nava.manne@xilinx.com>,
kbuild-all@01.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, michal.simek@xilinx.com,
soren.brinkmann@xilinx.com, balbi@ti.com,
gregkh@linuxfoundation.org, hyun.kwon@xilinx.com,
navam@xilinx.com, radhey.shyam.pandey@xilinx.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Axi-usb: Add support for 64-bit addressing.
Date: Sun, 17 Apr 2016 16:09:30 +0200 [thread overview]
Message-ID: <5220051.FEUC6vJBCk@wuerfel> (raw)
In-Reply-To: <201604111626.g2x2SCHX%fengguang.wu@intel.com>
On Monday 11 April 2016 16:08:14 kbuild test robot wrote:
>
> 230 * @offset: register offset
> 231 * @val: data to be written
> 232 **/
> 233 static void xudc_write64(void __iomem *addr, u32 offset, u64 val)
> 234 {
> 235 #if defined(CONFIG_PHYS_ADDR_T_64BIT)
> > 236 writeq(val, addr + offset);
> 237 #endif
> 238 }
>
I think you want lo_hi_writeq() rather than writeq().
Arnd
next prev parent reply other threads:[~2016-04-17 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 7:41 [PATCH] Axi-usb: Add support for 64-bit addressing Nava kishore Manne
[not found] ` <1460360506-14692-1-git-send-email-navam-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2016-04-11 8:08 ` kbuild test robot
2016-04-17 14:09 ` Arnd Bergmann [this message]
2016-04-12 14:03 ` Rob Herring
2016-04-17 13:14 ` Arnd Bergmann
2016-04-18 14:29 ` Rob Herring
2016-04-18 14:35 ` Arnd Bergmann
2016-04-19 9:15 ` Nava kishore Manne
[not found] ` <C89496FEAE474D468F30D558A9468D9F26CD3753-4lKfpRxZ5enZMOc0yg5rMog+Gb3gawCHQz34XiSyOiE@public.gmane.org>
2016-04-19 14:07 ` Arnd Bergmann
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=5220051.FEUC6vJBCk@wuerfel \
--to=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hyun.kwon@xilinx.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=nava.manne@xilinx.com \
--cc=navam@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=radhey.shyam.pandey@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=soren.brinkmann@xilinx.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;
as well as URLs for NNTP newsgroup(s).