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-next v7 1/5] ptp: clockmatrix: support 32-bit address space
Date: Thu, 14 Mar 2024 11:51:44 -0700 [thread overview]
Message-ID: <20240314115144.56836fe5@kernel.org> (raw)
In-Reply-To: <LV3P220MB120256EDF5276AB8F65C1ABDA0292@LV3P220MB1202.NAMP220.PROD.OUTLOOK.COM>
On Thu, 14 Mar 2024 11:37:03 -0400 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.
Please provide cover letters for series longer than 2 patches.
Apart from that:
## Form letter - net-next-closed
The merge window for v6.9 has begun and we have already posted our pull
request. Therefore net-next is closed for new drivers, features, code
refactoring and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens after March 25th.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
next prev parent reply other threads:[~2024-03-14 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 15:37 [PATCH net-next v7 1/5] ptp: clockmatrix: support 32-bit address space Min Li
2024-03-14 18:51 ` Jakub Kicinski [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-01-04 16:36 Min Li
2024-01-09 7:46 ` Paolo Abeni
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=20240314115144.56836fe5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.