public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh•net>
To: Jiri Kosina <jikos@kernel•org>, linux-input@vger•kernel.org
Cc: "Thomas Weißschuh" <linux@weissschuh•net>,
	"Stephen Rothwell" <sfr@canb•auug.org.au>,
	"Benjamin Tissoires" <benjamin.tissoires@redhat•com>,
	linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Subject: [PATCH] mod_devicetable: fix kdocs for ishtp_device_id
Date: Wed, 10 Nov 2021 13:16:55 +0100	[thread overview]
Message-ID: <20211110121655.675664-1-linux@weissschuh.net> (raw)
In-Reply-To: <20211110150639.7db57ae2@canb.auug.org.au>

The kdocs were copied from another device_id struct and not adapted.

Fixes: fa443bc3c1e4 ("HID: intel-ish-hid: add support for MODULE_DEVICE_TABLE()")
Signed-off-by: Thomas Weißschuh <linux@weissschuh•net>
---
 include/linux/mod_devicetable.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
index befbf53c4b7c..c70abe7aaef2 100644
--- a/include/linux/mod_devicetable.h
+++ b/include/linux/mod_devicetable.h
@@ -901,8 +901,7 @@ struct dfl_device_id {
 
 /**
  * struct ishtp_device_id - ISHTP device identifier
- * @guid_string: 36 char string of the form fa50ff2b-f2e8-45de-83fa-65417f2f49ba
- * @context: pointer to driver specific data
+ * @guid: GUID of the device.
  */
 struct ishtp_device_id {
 	guid_t guid;

base-commit: 7fb0413baa7f8a04caef0c504df9af7e0623d296
-- 
2.33.1


  parent reply	other threads:[~2021-11-10 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  4:06 linux-next: build warning after merge of the hid tree Stephen Rothwell
2021-11-10  8:17 ` Jiri Kosina
2021-11-10 12:16 ` Thomas Weißschuh [this message]
2021-11-10 12:20   ` [PATCH] mod_devicetable: fix kdocs for ishtp_device_id Jiri Kosina

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=20211110121655.675664-1-linux@weissschuh.net \
    --to=linux@weissschuh$(echo .)net \
    --cc=benjamin.tissoires@redhat$(echo .)com \
    --cc=jikos@kernel$(echo .)org \
    --cc=linux-input@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox