From: Al Viro <viro@zeniv.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-sh@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] sh: exports for delay.h
Date: Fri, 27 Dec 2024 16:22:22 +0000 [thread overview]
Message-ID: <20241227162222.GX1977892@ZenIV> (raw)
In-Reply-To: <CAMuHMdVpTtcT9LVGNvFLm4cvrNF=fe1dVsi2zo73Yee3oYrJYQ@mail.gmail.com>
On Fri, Dec 27, 2024 at 04:58:58PM +0100, Geert Uytterhoeven wrote:
> Please do not export __delay, as it is an internal implementation detail.
> Drivers should not call __delay() directly, as it has non-standardized
> semantics, or may not even exist.
As the matter of fact, it *does* exist and is either exported or a static
inline with everything used by it exported - on every architecture except sh.
next prev parent reply other threads:[~2024-12-27 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 22:22 [PATCH] sh: exports for delay.h Al Viro
2024-12-22 22:33 ` John Paul Adrian Glaubitz
2024-12-27 15:58 ` Geert Uytterhoeven
2024-12-27 16:22 ` Al Viro [this message]
2024-12-27 18:20 ` Geert Uytterhoeven
2024-12-27 18:31 ` Randy Dunlap
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=20241227162222.GX1977892@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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