From: laurentiu.tudor@nxp.com (Laurentiu Tudor)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] staging: fsl-mc: make the driver compile on other architectures
Date: Tue, 18 Jul 2017 14:43:45 +0000 [thread overview]
Message-ID: <596E1EA0.3040002@nxp.com> (raw)
In-Reply-To: <CAK8P3a39fpEHwCvR3TOL8u8W7TORSNpw27xwma70sxi-VfXhyA@mail.gmail.com>
Hi Arnd,
On 07/18/2017 05:26 PM, Arnd Bergmann wrote:
> On Tue, Jul 18, 2017 at 3:37 PM, <laurentiu.tudor@nxp.com> wrote:
>> From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
>>
>> Apart from a small change (first patch) which adds a missing comment,
>> this series make the bus driver compile on other architectures, as per
>> GregKH comment [1].
>> Compiled tested on:
>> - booke powerpc (corenet{32,64}_smp_defconfig) with this ppc patch [2]
>> - x86 (i386_defconfig, x86_64_defconfig, needs CONFIG_OF)
>> - arm64 (defconfig)
>>
>> [1] https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.spinics.net%2Flists%2Flinux-driver-devel%2Fmsg100585.html&data=01%7C01%7Claurentiu.tudor%40nxp.com%7C2564747d26964ed5b3f408d4cde8f442%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0&sdata=Dz8vvLzQESel2UTXrhQ3JZyNhx5VhUdj6%2BE6TDLnXmc%3D&reserved=0
>> [2] https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.ozlabs.org%2Fpatch%2F789474%2F&data=01%7C01%7Claurentiu.tudor%40nxp.com%7C2564747d26964ed5b3f408d4cde8f442%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0&sdata=%2FiGSaa4j60INeTWEbT926iEIAtya6tqIiIoQN1yFbmA%3D&reserved=0
>
> Looks good overall. With the two minor questions addressed
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
>
Thanks for the ack. I'll mention it the next version.
---
Thanks & Best Regards, Laurentiu
prev parent reply other threads:[~2017-07-18 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 13:37 [PATCH v2 0/7] staging: fsl-mc: make the driver compile on other architectures laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 1/8] staging: fsl-mc: add missing fsl_mc comment in struct msi_desc laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 2/8] staging: fsl-mc: use generic memory barriers laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 3/8] staging: fsl-mc: drop useless gic v3 related #include laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 4/8] staging: fsl-mc: fix compilation with non-generic msi domain ops laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 5/8] staging: fsl-mc: fix formating of phys_addr_t on 32 bits laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 6/8] staging: fsl-mc: don't use raw device io functions laurentiu.tudor at nxp.com
2017-07-18 14:18 ` Arnd Bergmann
2017-07-18 14:26 ` Laurentiu Tudor
2017-07-18 14:28 ` Arnd Bergmann
2017-07-18 13:37 ` [PATCH v2 7/8] staging: fsl-mc: make the driver compile on 32-bit laurentiu.tudor at nxp.com
2017-07-18 13:37 ` [PATCH v2 8/8] staging: fsl-mc: allow the driver compile multi-arch laurentiu.tudor at nxp.com
2017-07-18 14:25 ` Arnd Bergmann
2017-07-18 14:36 ` Laurentiu Tudor
2017-07-18 14:39 ` Arnd Bergmann
2017-07-18 14:26 ` [PATCH v2 0/7] staging: fsl-mc: make the driver compile on other architectures Arnd Bergmann
2017-07-18 14:43 ` Laurentiu Tudor [this message]
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=596E1EA0.3040002@nxp.com \
--to=laurentiu.tudor@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).