Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A723CC61DA4 for ; Sat, 11 Feb 2023 09:08:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229743AbjBKJGi (ORCPT ); Sat, 11 Feb 2023 04:06:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51512 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229447AbjBKJGg (ORCPT ); Sat, 11 Feb 2023 04:06:36 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 000C225E09; Sat, 11 Feb 2023 01:06:35 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6CF0960B80; Sat, 11 Feb 2023 09:06:35 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4B240C433D2; Sat, 11 Feb 2023 09:06:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1676106394; bh=UNe3vJq2Jm1T7RdXEmNdh8v4p8jdahu221bYz5Rbsa4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=iBpS53Sw+1hUTpR74BC0jld+p3oTylOg5MdW4szVKPT2v0yY4FX0oMSZrVj4tzT0l F0mMqTk9YJ2WDWZHhvtDzARUvYHF6HbkbQu6k5pneSzC929un9B7849JxC2V8Ign35 nu4Te0gEQIBm7ZEz91Oy9/Y2arp9aOfUTAzCLlIM= Date: Sat, 11 Feb 2023 10:06:31 +0100 From: Greg Kroah-Hartman To: Qi Zheng 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 Subject: Re: [PATCH 0/3] some minor fixes of error checking about debugfs_rename() Message-ID: References: <20230202093256.32458-1-zhengqi.arch@bytedance.com> <167548141786.31101.12461204128706467220.git-patchwork-notify@kernel.org> <20230207103124.052b5ce1@kernel.org> <420f2b78-2292-be4a-2e3f-cf0ed28f40d5@bytedance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <420f2b78-2292-be4a-2e3f-cf0ed28f40d5@bytedance.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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