From: Richard Cochran <richardcochran@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Min Li <lnimi@hotmail.com>,
lee@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Min Li <min.li.xe@renesas.com>
Subject: Re: [PATCH mfd 1/1] mfd/ptp: clockmatrix: support 32-bit address space
Date: Wed, 22 Mar 2023 19:46:22 -0700 [thread overview]
Message-ID: <ZBu9ftxTmtMc/BmG@hoboy.vegasvil.org> (raw)
In-Reply-To: <20230322125619.731912cf@kernel.org>
On Wed, Mar 22, 2023 at 12:56:19PM -0700, Jakub Kicinski wrote:
> Could you to split your patches into multiple steps to make them easier
> to reivew?
+1
I was thinking the same thing.
Thanks,
Richard
next prev parent reply other threads:[~2023-03-23 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 19:10 Min Li
2023-03-22 19:56 ` Jakub Kicinski
2023-03-23 2:46 ` Richard Cochran [this message]
2023-03-23 14:18 ` Min Li
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=ZBu9ftxTmtMc/BmG@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=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 \
/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®