From: Werner Sembach <wse@tuxedocomputers.com>
To: dmitry.torokhov@gmail.com, tiwai@suse.de, mpdesouza@suse.com,
arnd@arndb.de, hdegoede@redhat.com, samuel@cavoj.net,
wse@tuxedocomputers.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v5 1/4] input/i8042: Move __initconst to fix code styling warning
Date: Tue, 29 Mar 2022 16:36:19 +0200 [thread overview]
Message-ID: <20220329143622.31394-2-wse@tuxedocomputers.com> (raw)
In-Reply-To: <20220329143622.31394-1-wse@tuxedocomputers.com>
Move __intconst from before i8042_dmi_laptop_table[] to after it for
consistent code styling.
Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
Cc: stable@vger.kernel.org
---
drivers/input/serio/i8042-x86ia64io.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/serio/i8042-x86ia64io.h b/drivers/input/serio/i8042-x86ia64io.h
index 148a7c5fd0e2..91c6f24b4837 100644
--- a/drivers/input/serio/i8042-x86ia64io.h
+++ b/drivers/input/serio/i8042-x86ia64io.h
@@ -791,7 +791,7 @@ static const struct dmi_system_id __initconst i8042_dmi_nopnp_table[] = {
{ }
};
-static const struct dmi_system_id __initconst i8042_dmi_laptop_table[] = {
+static const struct dmi_system_id i8042_dmi_laptop_table[] __initconst = {
{
.matches = {
DMI_MATCH(DMI_CHASSIS_TYPE, "8"), /* Portable */
--
2.25.1
next prev parent reply other threads:[~2022-03-29 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 14:36 [PATCH v5] input/i8042: Rework quirk tables Werner Sembach
2022-03-29 14:36 ` Werner Sembach [this message]
2022-03-29 14:36 ` [PATCH v5 2/4] input/i8042: Merge " Werner Sembach
2022-03-29 14:36 ` [PATCH v5 3/4] input/i8042: Add debug output for quirks Werner Sembach
2022-03-29 14:36 ` [PATCH v5 4/4] input/i8042: Add TUXEDO devices to i8042 quirk tables Werner Sembach
2022-06-29 5:36 ` Dmitry Torokhov
2022-06-29 11:29 ` Werner Sembach
2022-03-29 14:41 ` [PATCH v5] input/i8042: Rework " Werner Sembach
2022-04-02 10:47 ` Hans de Goede
2022-04-04 14:36 ` Werner Sembach
2022-06-28 14:15 ` Werner Sembach
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=20220329143622.31394-2-wse@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=arnd@arndb.de \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdesouza@suse.com \
--cc=samuel@cavoj.net \
--cc=tiwai@suse.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