Re: [PATCH] [trivial] treewide: Fix typo in printk

From: Geert Uytterhoeven
Date: Thu Aug 28 2014 - 13:40:53 EST


On Thu, Aug 28, 2014 at 7:26 PM, Masanari Iida <standby24x7@xxxxxxxxx> wrote:
> diff --git a/arch/m68k/Kconfig.devices b/arch/m68k/Kconfig.devices
> index d163991..2a74777 100644
> --- a/arch/m68k/Kconfig.devices
> +++ b/arch/m68k/Kconfig.devices
> @@ -73,7 +73,7 @@ config ATARI_ETHERNEC
> ROM port. The driver works by polling instead of interrupts, so it
> is quite slow.
>
> - This driver also suppports the ethernet part of the NetUSBee ROM
> + This driver also supports the ethernet part of the NetUSBee ROM
> port combined Ethernet/USB adapter.

Acked-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>

BTW, there are a few more you may want to fix:

$ git grep supppor
arch/m68k/Kconfig.devices: This driver also suppports the ethernet
part of the NetUSBee ROM
drivers/scsi/esas2r/esas2r_flash.c: /* not suppported for now */;
drivers/scsi/mpt3sas/mpt3sas_ctl.c:/*********** diagnostic trigger
suppport *********************************/
drivers/scsi/mpt3sas/mpt3sas_ctl.c:/*********** diagnostic trigger
suppport *** END ****************************/
drivers/staging/comedi/drivers/pcmuio.c: /* subdevices 0 and 2 can
suppport interrupts */
drivers/usb/gadget/udc/Kconfig: high speed or full speed USB device.
This driver supppors
fs/f2fs/f2fs.h: /* For sysfs suppport */
include/uapi/linux/nl80211.h: * to work properly to suppport receiving
regulatory hints from
kernel/trace/trace.h: * Now if the arch does not suppport a feature,
and it calls

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/