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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 30 Apr 2020 21:30:17 +0200
From:   Ard Biesheuvel <ardb@...nel.org>
To:     Joe Perches <joe@...ches.com>
Cc:     Arvind Sankar <nivedita@...m.mit.edu>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-efi <linux-efi@...r.kernel.org>, X86 ML <x86@...nel.org>
Subject: Re: [PATCH 2/2] efi/libstub: Correct comment typos

On Thu, 30 Apr 2020 at 21:12, Joe Perches <joe@...ches.com> wrote:
>
> Fix a couple typos in comments.
>
> Signed-off-by: Joe Perches <joe@...ches.com>

Thanks, I'll queue this one up

> ---
>
> Perhaps these trivialities on top of this series?
>
> drivers/firmware/efi/libstub/pci.c      | 2 +-
>  drivers/firmware/efi/libstub/relocate.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/firmware/efi/libstub/pci.c b/drivers/firmware/efi/libstub/pci.c
> index 111c44b..17a53d8 100644
> --- a/drivers/firmware/efi/libstub/pci.c
> +++ b/drivers/firmware/efi/libstub/pci.c
> @@ -69,7 +69,7 @@ void efi_pci_disable_bridge_busmaster(void)
>                  * access to the framebuffer. Drivers for true PCIe graphics
>                  * controllers that are behind a PCIe root port do not use
>                  * DMA to implement the GOP framebuffer anyway [although they
> -                * may use it in their implentation of Gop->Blt()], and so
> +                * may use it in their implementation of Gop->Blt()], and so
>                  * disabling DMA in the PCI bridge should not interfere with
>                  * normal operation of the device.
>                  */
> diff --git a/drivers/firmware/efi/libstub/relocate.c b/drivers/firmware/efi/libstub/relocate.c
> index 62e2d6..a7ad26 100644
> --- a/drivers/firmware/efi/libstub/relocate.c
> +++ b/drivers/firmware/efi/libstub/relocate.c
> @@ -140,7 +140,7 @@ efi_status_t efi_relocate_kernel(unsigned long *image_addr,
>          * The EFI firmware loader could have placed the kernel image
>          * anywhere in memory, but the kernel has restrictions on the
>          * max physical address it can run at.  Some architectures
> -        * also have a prefered address, so first try to relocate
> +        * also have a preferred address, so first try to relocate
>          * to the preferred address.  If that fails, allocate as low
>          * as possible while respecting the required alignment.
>          */
> --
> 2.26.0
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ