From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Roger Quadros <rogerq@kernel.org>
Cc: linux-omap@vger.kernel.org, nm@ti.com,
linux-kernel@vger.kernel.org, kishon@ti.com, tony@atomide.com,
miquel.raynal@bootlin.com, vigneshr@ti.com
Subject: Re: [PATCH v3 0/2] memory: omap-gpmc: Allow module build
Date: Wed, 13 Apr 2022 15:00:55 +0200 [thread overview]
Message-ID: <897a05fd-a568-9d33-dc20-5de4e5d2188f@linaro.org> (raw)
In-Reply-To: <4681b00e-7f89-d9c4-6361-b781ced72656@kernel.org>
On 13/04/2022 14:56, Roger Quadros wrote:
>>
>> If you have spare time, maybe you could investigate the compile testing
>> on other platforms as well and if something fails, fix it. But it seems
>> it is separate problem.
>>
>
> I won't be able to test on all platforms. I'm ok to not add more dependency and
> just drop COMPILE_TEST.
I understand that. You can still test 8-12 popular ones on a regular
Ubuntu machine (there are like 10 or 12 cross compile toolchains now in
standard Ubuntu repos).
Another way is to put your patches on Github and ask kbuild folks to
test your trees. I think this was the repo (but double check):
https://github.com/fengguang/lkp-tests
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-13 13:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 9:55 [PATCH v3 0/2] memory: omap-gpmc: Allow module build Roger Quadros
2022-04-11 9:55 ` [PATCH v3 1/2] memory: omap-gpmc: Make OMAP_GPMC config visible and selectable Roger Quadros
2022-04-11 10:06 ` Miquel Raynal
2022-04-11 9:55 ` [PATCH v3 2/2] memory: omap-gpmc: Allow building as a module Roger Quadros
2022-04-13 9:43 ` [PATCH v3 0/2] memory: omap-gpmc: Allow module build Krzysztof Kozlowski
2022-04-13 9:50 ` Krzysztof Kozlowski
2022-04-13 10:20 ` Krzysztof Kozlowski
2022-04-13 10:42 ` Roger Quadros
2022-04-13 11:01 ` Roger Quadros
2022-04-13 11:05 ` Krzysztof Kozlowski
2022-04-13 11:33 ` Roger Quadros
2022-04-13 11:47 ` Krzysztof Kozlowski
2022-04-13 11:56 ` Roger Quadros
2022-04-13 12:31 ` Krzysztof Kozlowski
2022-04-13 12:56 ` Roger Quadros
2022-04-13 13:00 ` Krzysztof Kozlowski [this message]
2022-04-13 13:04 ` Krzysztof Kozlowski
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=897a05fd-a568-9d33-dc20-5de4e5d2188f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=nm@ti.com \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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