From: Jakub Kicinski <kuba@kernel.org>
To: Min Li <lnimi@hotmail.com>
Cc: richardcochran@gmail.com, lee@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Min Li <min.li.xe@renesas.com>
Subject: Re: [PATCH net RFC 1/1] mfd/ptp: clockmatrix: support 32-bit address space
Date: Tue, 24 Jan 2023 19:06:01 -0800 [thread overview]
Message-ID: <20230124190601.6150f86d@kernel.org> (raw)
In-Reply-To: <MW5PR03MB69325F46D3E3B6473A228D1FA0C99@MW5PR03MB6932.namprd03.prod.outlook.com>
On Tue, 24 Jan 2023 10:41:09 -0500 Min Li wrote:
> From: Min Li <min.li.xe@renesas.com>
>
> We used to assume 0x2010xxxx address. Now that we
> need to access 0x2011xxxx address, we need to
> support read/write the whole 32-bit address space.
Fist of all - you need to say a bit more about what you're doing.
You based this on net which would indicate it's a fix but it's enormous.
next prev parent reply other threads:[~2023-01-25 3:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 15:41 [PATCH net RFC 1/1] mfd/ptp: clockmatrix: support 32-bit address space Min Li
2023-01-25 3:06 ` Jakub Kicinski [this message]
2023-01-25 14:36 ` Simon Horman
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=20230124190601.6150f86d@kernel.org \
--to=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lnimi@hotmail.com \
--cc=min.li.xe@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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).