From: Paolo Abeni <pabeni@redhat.com>
To: Min Li <lnimi@hotmail.com>, richardcochran@gmail.com, lee@kernel.org
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Min Li <min.li.xe@renesas.com>
Subject: Re: [PATCH net-next v7 1/5] ptp: clockmatrix: support 32-bit address space
Date: Tue, 09 Jan 2024 08:46:17 +0100 [thread overview]
Message-ID: <8a06f42e3a7028f88920764d5a70637a6a174eac.camel@redhat.com> (raw)
In-Reply-To: <PH7PR03MB7064B821752DCD99610ED72CA0672@PH7PR03MB7064.namprd03.prod.outlook.com>
On Thu, 2024-01-04 at 11:36 -0500, Min Li wrote:
> @@ -553,11 +554,11 @@ static int _sync_pll_output(struct idtcm *idtcm,
> val = SYNCTRL1_MASTER_SYNC_RST;
>
> /* Place master sync in reset */
> - err = idtcm_write(idtcm, 0, sync_ctrl1, &val, sizeof(val));
> + err = idtcm_write(idtcm, sync_ctrl1, 0, &val, sizeof(val));
> if (err)
> return err;
I'm sorry for the late feedback: I lost track the last replies in the
previous revision and later I was on PTO.
Let me extract the relevant slice from such thread:
On Wed, 13 Dec 2023 21:04:07 +0000 Min Li wrote:
> > My reading is that this patch reverses the usage of module and regaddr.
> > F.e. the following hunk:
> >
> > @@ -553,11 +554,11 @@ static int _sync_pll_output(struct idtcm *idtcm,
> > val = SYNCTRL1_MASTER_SYNC_RST;
> >
> > /* Place master sync in reset */
> > err = idtcm_write(idtcm, 0, sync_ctrl1, &val, sizeof(val));
> > err = idtcm_write(idtcm, sync_ctrl1, 0, &val, sizeof(val));
> > if (err)
> > return err;
> >
> > err = idtcm_write(idtcm, 0, sync_ctrl0, &sync_src, sizeof(sync_src));
> > err = idtcm_write(idtcm, sync_ctrl0, 0, &sync_src, sizeof(sync_src));
> > if (err)
> > return err;
> >
> > If that is really intended I think it needs to be explained, or possibly a
> > separate patch.
>
> Hi Simon
> sync_ctrl0/1 was meant to be a module and it was in a wrong place.
> And this patch is just correcting it.
Then you need to move this chunk (and all the later on swapping the
'address' and the 'module' argument in a separate patch. Mixing this
fix and the address space extension is confusing.
Additionally we are currently preparing the net-next PR for 6.8 and I
don't feel very confident to apply such a large refactor this late. I
think it should be better postpone to the next cycle.
Cheers,
Paolo
next prev parent reply other threads:[~2024-01-09 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 16:36 Min Li
2024-01-09 7:46 ` Paolo Abeni [this message]
[not found] <20240501160324.27514-1-lnimi@hotmail.com>
2024-05-01 16:03 ` Min Li
[not found] <20240318173213.28475-1-lnimi@hotmail.com>
2024-03-18 17:32 ` Min Li
-- strict thread matches above, loose matches on Subject: below --
2024-03-14 15:37 Min Li
2024-03-14 18:51 ` Jakub Kicinski
2023-12-14 15:24 Min Li
2024-01-02 14:31 ` 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=8a06f42e3a7028f88920764d5a70637a6a174eac.camel@redhat.com \
--to=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®