linux-kernel - Re: [PATCH 0/3] some minor fixes of error checking about debugfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Y+4mY9L++tWBSQ+t@kroah.com>
Date:   Thu, 16 Feb 2023 13:49:39 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Qi Zheng <zhengqi.arch@...edance.com>
Cc:     patchwork-bot+netdevbpf@...nel.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, Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH 0/3] some minor fixes of error checking about
 debugfs_rename()

On Sat, Feb 11, 2023 at 05:12:46PM +0800, Qi Zheng wrote:
> 
> 
> On 2023/2/11 17:06, Greg Kroah-Hartman wrote:
> > 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.
> No worries. And the patch link that has been resent is
> https://lore.kernel.org/lkml/20230208035634.58095-1-zhengqi.arch@bytedance.com/.
> :)

Both now queued up, thanks.

greg k-h