Linux kernel staging patches
 help / color / mirror / Atom feed
From: Dorian Catric <dorian.catric@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, marvin24@gmx.de,
	Dorian Catric <dorian.catric@gmail.com>
Subject: [PATCH] staging: nvec: fix coding style issues in nvec.c
Date: Tue,  2 Jun 2026 22:52:52 +0200	[thread overview]
Message-ID: <20260602205252.3336-1-dorian.catric@gmail.com> (raw)

Fix three coding style issues detected by checkpatch.pl:

- Fix typo in URL: 'lauchpad.net' -> 'launchpad.net' in the copyright
  header (nvec.h already has the correct spelling)
- Remove extra space in 'enum nvec_msg_category  {' declaration
- Convert EXPORT_SYMBOL() to EXPORT_SYMBOL_GPL() for nvec_write_async()
  and nvec_write_sync() to match the other exported symbols in this driver

Signed-off-by: Dorian Catric <dorian.catric@gmail.com>
---
 drivers/staging/nvec/nvec.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
index 952c5a849a563..f14d9a1eb2ed5 100644
--- a/drivers/staging/nvec/nvec.c
+++ b/drivers/staging/nvec/nvec.c
@@ -2,7 +2,7 @@
 /*
  * NVEC: NVIDIA compliant embedded controller interface
  *
- * Copyright (C) 2011 The AC100 Kernel Team <ac100@lists.lauchpad.net>
+ * Copyright (C) 2011 The AC100 Kernel Team <ac100@lists.launchpad.net>
  *
  * Authors:  Pierre-Hugues Husson <phhusson@free.fr>
  *           Ilya Petrov <ilya.muromec@gmail.com>
@@ -57,7 +57,7 @@
  * @NVEC_MSG_RX: The message is an incoming message (from EC)
  * @NVEC_MSG_TX: The message is an outgoing message (to EC)
  */
-enum nvec_msg_category  {
+enum nvec_msg_category {
 	NVEC_MSG_RX,
 	NVEC_MSG_TX,
 };
@@ -275,7 +275,7 @@ int nvec_write_async(struct nvec_chip *nvec, const unsigned char *data,
 
 	return 0;
 }
-EXPORT_SYMBOL(nvec_write_async);
+EXPORT_SYMBOL_GPL(nvec_write_async);
 
 /**
  * nvec_write_sync - Write a message to nvec and read the response
@@ -331,7 +331,7 @@ int nvec_write_sync(struct nvec_chip *nvec,
 
 	return 0;
 }
-EXPORT_SYMBOL(nvec_write_sync);
+EXPORT_SYMBOL_GPL(nvec_write_sync);
 
 /**
  * nvec_toggle_global_events - enables or disables global event reporting
-- 
2.34.1


             reply	other threads:[~2026-06-02 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 20:52 Dorian Catric [this message]
2026-06-03  6:35 ` [PATCH] staging: nvec: fix coding style issues in nvec.c Dan Carpenter

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=20260602205252.3336-1-dorian.catric@gmail.com \
    --to=dorian.catric@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=marvin24@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox