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 mfd-n 1/2] ptp: clockmatrix: support 32-bit address space
Date: Thu, 23 Mar 2023 09:56:26 -0700 [thread overview]
Message-ID: <20230323095626.14d6d4da@kernel.org> (raw)
In-Reply-To: <MW5PR03MB69324DE0DEA03E3C62C57447A0879@MW5PR03MB6932.namprd03.prod.outlook.com>
On Thu, 23 Mar 2023 12:15:17 -0400 Min Li wrote:
> - err = idtcm_write(idtcm, 0, HW_Q8_CTRL_SPARE,
> + err = idtcm_write(idtcm, HW_Q8_CTRL_SPARE, 0,
> &temp, sizeof(temp));
The flipping of the arguments should also be a separate patch.
next prev parent reply other threads:[~2023-03-23 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 16:15 [PATCH mfd-n 1/2] ptp: clockmatrix: support 32-bit address space Min Li
2023-03-23 16:56 ` Jakub Kicinski [this message]
2023-03-27 14:54 ` Min Li
2023-03-27 17:37 ` Jakub Kicinski
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=20230323095626.14d6d4da@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).