linux-kernel - Re: [PATCH] driver core: fix comments for device_block

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: <CAJZ5v0gHicDbshzv=WJP-sTLfj8Cmt2fyu3uyy+jaQ3OOOBUmA@mail.gmail.com>
Date:   Tue, 6 Nov 2018 08:52:42 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH] driver core: fix comments for device_block_probing()

On Tue, Nov 6, 2018 at 8:41 AM Randy Dunlap <rdunlap@...radead.org> wrote:
>
> From: Randy Dunlap <rdunlap@...radead.org>
>
> Correct function name and spelling/typo for device_block_probing()
> in drivers/base/dd.c.
>
> Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: "Rafael J. Wysocki" <rafael@...nel.org>

Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>

> ---
>  drivers/base/dd.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- lnx-420-rc1.orig/drivers/base/dd.c
> +++ lnx-420-rc1/drivers/base/dd.c
> @@ -179,7 +179,7 @@ static void driver_deferred_probe_trigge
>  }
>
>  /**
> - * device_block_probing() - Block/defere device's probes
> + * device_block_probing() - Block/defer device's probes
>   *
>   *     It will disable probing of devices and defer their probes instead.
>   */
> @@ -453,7 +453,7 @@ static int really_probe(struct device *d
>         if (defer_all_probes) {
>                 /*
>                  * Value of defer_all_probes can be set only by
> -                * device_defer_all_probes_enable() which, in turn, will call
> +                * device_block_probing() which, in turn, will call
>                  * wait_for_device_probe() right after that to avoid any races.
>                  */
>                 dev_dbg(dev, "Driver %s force probe deferral\n", drv->name);
>
>