All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qi Zheng <zhengqi.arch@bytedance.com>
To: patchwork-bot+netdevbpf@kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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
Subject: Re: [PATCH 0/3] some minor fixes of error checking about debugfs_rename()
Date: Tue, 7 Feb 2023 18:30:40 +0800	[thread overview]
Message-ID: <aeae8fb8-b052-0d4a-5d3e-8de81e1b5092@bytedance.com> (raw)
In-Reply-To: <167548141786.31101.12461204128706467220.git-patchwork-notify@kernel.org>



On 2023/2/4 11:30, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
> 
> This series was applied to netdev/net.git (master)
> by Jakub Kicinski <kuba@kernel.org>:
> 
> On Thu,  2 Feb 2023 17:32:53 +0800 you wrote:
>> Since commit ff9fb72bc077 ("debugfs: return error values, not NULL") changed
>> return value of debugfs_rename() in error cases from %NULL to %ERR_PTR(-ERROR).
>> The comments and checks corresponding to debugfs_rename() should also be updated
>> and fixed.
>>
>> Qi Zheng (3):
>>    debugfs: update comment of debugfs_rename()
>>    bonding: fix error checking in bond_debug_reregister()
>>    PM/OPP: fix error checking in opp_migrate_dentry()
>>
>> [...]
> 
> 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)

Hi all,

Does "no matching commit" means that these two patches have not been
applied? And I did not see them in the linux-next branch.

If so, hi Greg, Can you help to review and apply these two patches
([1/3] and [3/3])?

Thanks,
Qi

> 
> You are awesome, thank you!

-- 
Thanks,
Qi

  reply	other threads:[~2023-02-07 10:31 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 [this message]
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
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=aeae8fb8-b052-0d4a-5d3e-8de81e1b5092@bytedance.com \
    --to=zhengqi.arch@bytedance.com \
    --cc=andy@greyhouse.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=j.vosburgh@gmail.com \
    --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 \
    /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.