All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Metehan Günen" <metehangnen@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH 2/4] drivers/misc: add Goodix GXFP5130 eSPI fingerprint sensor driver
Date: Sat, 18 Jul 2026 11:09:43 +0200	[thread overview]
Message-ID: <2026071828-blunt-survivor-834f@gregkh> (raw)
In-Reply-To: <20260718081431.25456-3-metehangnen@gmail.com>

On Sat, Jul 18, 2026 at 11:14:29AM +0300, Metehan Günen wrote:
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -651,4 +651,6 @@ source "drivers/misc/mchp_pci1xxxx/Kconfig"
>  source "drivers/misc/keba/Kconfig"
>  source "drivers/misc/amd-sbi/Kconfig"
>  source "drivers/misc/rp1/Kconfig"
> +source "drivers/misc/gxfp5130/Kconfig"
> +

Why add this extra line?

>  endmenu
> diff --git a/drivers/misc/Makefile b/drivers/misc/Makefile
> index fed47c767..e85c68aa1 100644
> --- a/drivers/misc/Makefile
> +++ b/drivers/misc/Makefile
> @@ -74,3 +74,5 @@ obj-$(CONFIG_MCHP_LAN966X_PCI)	+= lan966x-pci.o
>  obj-y				+= keba/
>  obj-y				+= amd-sbi/
>  obj-$(CONFIG_MISC_RP1)		+= rp1/
> +
> +obj-$(CONFIG_GXFP5130)		+= gxfp5130/

Same here, why the extra line?

> +	gxfp_trace_logf("cmd_timeout req=0x%02x expect=0x%02x tries=%u",
> +		req->req_cmd, req->expect_cmd, req->tries ? req->tries : 1);

Please do not roll your own tracing functions, use the in-kernel ones
instead.

thanks,

greg k-h

  reply	other threads:[~2026-07-18  9:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18  8:14 [PATCH 0/4] drivers/misc: add Goodix GXFP5130 eSPI fingerprint sensor driver Metehan Günen
2026-07-18  8:14 ` [PATCH 1/4] include/uapi/linux: add gxfp_ioctl.h for GXFP5130 fingerprint sensor Metehan Günen
2026-07-18  9:07   ` Greg KH
2026-07-18  9:08   ` Greg KH
2026-07-18  8:14 ` [PATCH 2/4] drivers/misc: add Goodix GXFP5130 eSPI fingerprint sensor driver Metehan Günen
2026-07-18  9:09   ` Greg KH [this message]
2026-07-18  9:12   ` Greg KH
2026-07-18  8:14 ` [PATCH 3/4] Documentation/misc-devices: add gxfp5130.rst Metehan Günen
2026-07-18  9:06   ` Greg KH
2026-07-18  8:14 ` [PATCH 4/4] MAINTAINERS: add entry for GXFP5130 fingerprint sensor driver Metehan Günen
2026-07-18  9:06   ` Greg KH
2026-07-18  9:05 ` [PATCH 0/4] drivers/misc: add Goodix GXFP5130 eSPI " Greg KH

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=2026071828-blunt-survivor-834f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=metehangnen@gmail.com \
    /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.