From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Brock.Zheng" <yzheng@techyauld.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memory: omap-gpmc: fixup wrongly hierarchy of the sub-devices
Date: Fri, 1 Mar 2024 12:40:36 +0100 [thread overview]
Message-ID: <cfec2fee-ebd8-4865-b307-b64e1bbfa335@linaro.org> (raw)
In-Reply-To: <6fftq2zlkpaf7xptyff6ky63cinr76ziyvdbm5jhj2apubr5vf@l4gvbdax3l2e>
On 01/03/2024 00:52, Brock.Zheng wrote:
> On TI-AM335x，my FPGA under GPMC local-bus can not work on 6.x kernel.
>
> GPMC <--> FPGA <--> sub-devices....
>
> I found that the platform sub-devices is in wrongly organized
> hierarchy. The grandchildren are now under the GPMC device
> directly, not under it's father(FPGA).
>
> Signed-off-by: Brock.Zheng <yzheng@techyauld.com>
The dot '.' does not look like part of the name. Are you sure you
transliterated/translated your name correctly?
Also, please provide Fixes tag (see submitting patches document).
Your patch confused my mailer. It looks like HTML, but it seems it is
not. Maybe because of Content-Disposition: inline? Why do you have it?
Best regards,
Krzysztof
prev parent reply other threads:[~2024-03-01 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 23:52 [PATCH] memory: omap-gpmc: fixup wrongly hierarchy of the sub-devices Brock.Zheng
2024-03-01 11:22 ` Roger Quadros
2024-03-01 12:38 ` Andreas Kemnade
2024-03-01 13:41 ` Roger Quadros
2024-03-01 23:57 ` [PATCH] memory/omap-gpmc: " Brock Zheng
2024-03-02 16:25 ` Krzysztof Kozlowski
[not found] ` <beacb55c-951b-4177-83ab-94fda44cd2b7@kernel.org>
2024-03-03 8:18 ` [PATCH] memory: omap-gpmc: " Brock Zheng
2024-03-05 9:55 ` Roger Quadros
2024-03-08 16:48 ` Krzysztof Kozlowski
2024-03-26 9:09 ` Krzysztof Kozlowski
2024-03-01 11:40 ` Krzysztof Kozlowski [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=cfec2fee-ebd8-4865-b307-b64e1bbfa335@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
--cc=yzheng@techyauld.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