From: Linus Walleij <linus.walleij@linaro.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [linux-next:master 1581/2065] drivers/base/regmap/regmap-mmio.c:231:17: error: implicit declaration of function 'writesq'; did you mean 'writeq'?
Date: Thu, 18 Aug 2022 10:02:34 +0200 [thread overview]
Message-ID: <CACRpkdZ4fNnmCt5gdqsUXEGfVk1nZUr=kO=8ysWVr-SGb93Frw@mail.gmail.com> (raw)
In-Reply-To: <202208181447.G9FLcMkI-lkp@intel.com>
On Thu, Aug 18, 2022 at 8:35 AM kernel test robot <lkp@intel.com> wrote:
> config: alpha-randconfig-r031-20220818
> compiler: alpha-linux-gcc (GCC) 12.1.0
So Alpha doesn't support readsq/writesq despite being 64bit?
OK I guess I have to send another API contract fix...
What's good with regmap being used all over the place
is that it brings this kind of semantic dissonance out into
the light.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-08-18 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 6:35 kernel test robot
2022-08-18 8:02 ` Linus Walleij [this message]
2022-08-18 11:57 ` Linus Walleij
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='CACRpkdZ4fNnmCt5gdqsUXEGfVk1nZUr=kO=8ysWVr-SGb93Frw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=broonie@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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