From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: patchwork-bot+netdevbpf@kernel.org, rafael@kernel.org,
j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
vireshk@kernel.org, nm@ti.com, sboyd@kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 0/3] some minor fixes of error checking about debugfs_rename()
Date: Sat, 11 Feb 2023 10:06:31 +0100 [thread overview]
Message-ID: <Y+dal7QKULCa+mb4@kroah.com> (raw)
In-Reply-To: <420f2b78-2292-be4a-2e3f-cf0ed28f40d5@bytedance.com>
On Wed, Feb 08, 2023 at 08:05:44PM +0800, Qi Zheng wrote:
>
>
> On 2023/2/8 19:54, Greg Kroah-Hartman wrote:
> > On Tue, Feb 07, 2023 at 10:31:24AM -0800, Jakub Kicinski wrote:
> > > On Tue, 7 Feb 2023 18:30:40 +0800 Qi Zheng wrote:
> > > > > Here is the summary with links:
> > > > > - [1/3] debugfs: update comment of debugfs_rename()
> > > > > (no matching commit)
> > > > > - [2/3] bonding: fix error checking in bond_debug_reregister()
> > > > > https://git.kernel.org/netdev/net/c/cbe83191d40d
> > > > > - [3/3] PM/OPP: fix error checking in opp_migrate_dentry()
> > > > > (no matching commit)
> > > >
> > > > Does "no matching commit" means that these two patches have not been
> > > > applied? And I did not see them in the linux-next branch.
> > >
> > > Correct, we took the networking patch to the networking tree.
> > > You'd be better off not grouping patches from different subsystems
> > > if there are no dependencies. Maintainers may get confused about
> > > who's supposed to apply them, err on the side of caution and
> > > not apply anything.
> > >
> > > > If so, hi Greg, Can you help to review and apply these two patches
> > > > ([1/3] and [3/3])?
> >
> > If someone sends me patch 1, I can and will review it then. Otherwise,
> > digging it out of a random patch series is pretty impossible with my
> > patch load, sorry.
>
> Hi Greg,
>
> Sorry about this. My bad. And I have sent the [1/3] separately, please
> review it if you have time. :)
Ick, somehow all of these got marked as spam by my filters. I'll look
at them next week, sorry for the delay.
greg k-h
next prev parent reply other threads:[~2023-02-11 9:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 9:32 [PATCH 0/3] some minor fixes of error checking about debugfs_rename() Qi Zheng
2023-02-02 9:32 ` [PATCH 1/3] debugfs: update comment of debugfs_rename() Qi Zheng
2023-02-02 9:32 ` [PATCH 2/3] bonding: fix error checking in bond_debug_reregister() Qi Zheng
2023-02-02 18:41 ` Jay Vosburgh
2023-02-02 9:32 ` [PATCH 3/3] PM/OPP: fix error checking in opp_migrate_dentry() Qi Zheng
2023-02-04 3:30 ` [PATCH 0/3] some minor fixes of error checking about debugfs_rename() patchwork-bot+netdevbpf
2023-02-07 10:30 ` Qi Zheng
2023-02-07 18:31 ` Jakub Kicinski
2023-02-08 2:51 ` Qi Zheng
2023-02-08 11:54 ` Greg Kroah-Hartman
2023-02-08 12:05 ` Qi Zheng
2023-02-11 9:06 ` Greg Kroah-Hartman [this message]
2023-02-11 9:12 ` Qi Zheng
2023-02-16 12:49 ` Greg Kroah-Hartman
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=Y+dal7QKULCa+mb4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy@greyhouse.net \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=vfalico@gmail.com \
--cc=vireshk@kernel.org \
--cc=zhengqi.arch@bytedance.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.