From: Tony Lindgren <tony@atomide.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:GENERIC INCLUDE/ASM HEADER FILES"
<linux-arch@vger.kernel.org>, Dave Gerlach <d-gerlach@ti.com>,
Keerthy J <j-keerthy@ti.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-omap@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH 1/3] ARM: Generalize fncpy implementation
Date: Fri, 16 Jun 2017 01:35:24 -0700 [thread overview]
Message-ID: <20170616083524.GJ3730@atomide.com> (raw)
In-Reply-To: <577f22f3-ff16-05a0-8204-39e86d47dd9f@gmail.com>
* Florian Fainelli <f.fainelli@gmail.com> [170615 16:27]:
> On 06/15/2017 04:21 PM, Florian Fainelli wrote:
> > ARM's fncpy implementation is actually suitable for a large number of
> > platforms since the only assumption it makes is just the function's
> > alignment (8 bytes) which also happens to fulfil other architectures,
> > including but not limited to ARM64.
Yeah I'm all for it. Maybe mention in the next version that this helps
with making SoC specific PM code into just regular Linux device drivers.
Regards,
Tony
next prev parent reply other threads:[~2017-06-16 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 23:21 [PATCH 0/3] Generalize fncpy availability Florian Fainelli
2017-06-15 23:21 ` [PATCH 1/3] ARM: Generalize fncpy implementation Florian Fainelli
2017-06-15 23:21 ` Florian Fainelli
2017-06-15 23:23 ` Florian Fainelli
2017-06-16 8:35 ` Tony Lindgren [this message]
2017-06-16 8:35 ` Tony Lindgren
2017-06-16 11:58 ` Russell King - ARM Linux
2017-06-15 23:21 ` [PATCH 2/3] arm64: Provide a fncpy implenentation Florian Fainelli
2017-06-15 23:21 ` [PATCH 3/3] misc: sram: Allow ARM64 to select SRAM_EXEC Florian Fainelli
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=20170616083524.GJ3730@atomide.com \
--to=tony@atomide.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=d-gerlach@ti.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=j-keerthy@ti.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=shawnguo@kernel.org \
--cc=will.deacon@arm.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).