[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2dea582a-acb1-c0f5-2e59-8d14470e380a@bytedance.com>
Date: Wed, 8 Feb 2023 10:51:05 +0800
From: Qi Zheng <zhengqi.arch@...edance.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, rafael@...nel.org,
j.vosburgh@...il.com, vfalico@...il.com, andy@...yhouse.net,
vireshk@...nel.org, nm@...com, sboyd@...nel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH 0/3] some minor fixes of error checking about
debugfs_rename()
On 2023/2/8 02:31, 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.
>
Hi Jakub,
> Correct, we took the networking patch to the networking tree.
Thank you very much. :)
> 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.
Got it. I will send [1/3] and [3/3] separately.
>
>> If so, hi Greg, Can you help to review and apply these two patches
>> ([1/3] and [3/3])?
>
> Or 3/3 should go to Viresh?.. Dunno..
Got it.
Thanks,
Qi
Powered by blists - more mailing lists