From: Andrew Lunn <andrew@lunn.ch>
To: 张网 <m202171703@hust.edu.cn>
Cc: hust-os-kernel-patches@googlegroups.com,
peter korsgaard <peter@korsgaard.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v3] i2c: ocores: use devm_ managed clks
Date: Tue, 23 May 2023 14:10:34 +0200 [thread overview]
Message-ID: <c5c8d9f7-ed50-4650-a5ac-b481999212cf@lunn.ch> (raw)
In-Reply-To: <5572a733.abc0.18846f13b0b.Coremail.m202171703@hust.edu.cn>
> Hi Andrew,
> I'm checking in about my patch submission for i2c ocores that was
> "review'ed" on 4/25, but its status has not been updated yet.
> I would greatly appreciate it if you could provide me with an
> update on the status of my submission. Is there any additional
> information or documentation that I can provide to help expedite
> the process?
I think your patch was submitted during the merge window. This is the
point in time when subsystems give Linus patches for the next
release. During those two weeks new patches are not accepted.
https://www.kernel.org/doc/html/latest/process/2.Process.html
Now that the merge window is closed, please rebase your patch on
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
and resubmit. Include my Reviewed-by tag.
Andrew
next prev parent reply other threads:[~2023-05-23 12:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 7:20 [PATCH] i2c: ocores: add missing unwind goto in `ocores_i2c_probe` Wang Zhang
2023-04-16 15:33 ` Andrew Lunn
2023-04-17 13:27 ` [PATCH v2] i2c: ocores: use devm_ managed clks Wang Zhang
2023-04-17 14:05 ` Wang Zhang
2023-04-17 14:29 ` Peter Rosin
2023-04-17 15:50 ` Andrew Lunn
2023-04-22 12:32 ` [PATCH v3] " Wang Zhang
2023-04-25 9:58 ` 张网
2023-04-25 11:57 ` Andrew Lunn
2023-04-25 14:47 ` 张网
2023-04-25 15:06 ` Andrew Lunn
2023-05-26 7:05 ` [PATCH v4] " Wang Zhang
2023-06-13 23:54 ` Andi Shyti
2023-06-23 8:22 ` Wolfram Sang
2023-06-23 8:26 ` Wolfram Sang
2023-05-23 4:49 ` Re: [PATCH v3] " 张网
2023-05-23 12:10 ` Andrew Lunn [this message]
2023-05-23 14:33 ` Wang Zhang
2023-05-24 15:35 ` Wang Zhang
2023-05-24 15:43 ` Wang Zhang
2023-05-24 18:45 ` Dan Carpenter
2023-05-24 19:21 ` Christophe JAILLET
2023-05-25 3:33 ` 张网
2023-05-25 19:16 ` Christophe JAILLET
2023-05-25 5:05 ` Dan Carpenter
2023-05-25 5:02 ` Dan Carpenter
2023-05-25 9:28 ` Dan Carpenter
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=c5c8d9f7-ed50-4650-a5ac-b481999212cf@lunn.ch \
--to=andrew@lunn.ch \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m202171703@hust.edu.cn \
--cc=peter@korsgaard.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).