From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Boris Brezillon" <bbrezillon@kernel.org>,
"Przemysław Gaj" <pgaj@cadence.com>,
"Vitor Soares" <Vitor.Soares@synopsys.com>,
linux-i3c@lists.infradead.org
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] i3c: Fix MODALIAS uevents
Date: Sat, 22 Feb 2020 11:27:09 +0100 [thread overview]
Message-ID: <20200222102711.1352006-2-boris.brezillon@collabora.com> (raw)
In-Reply-To: <20200222102711.1352006-1-boris.brezillon@collabora.com>
file2alias uses %X formatters. Fix typos in the MODALIAS uevent to print
the part and ext IDs in uppercase.
Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
---
drivers/i3c/master.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
index b56207bbed2b..b6db82862a63 100644
--- a/drivers/i3c/master.c
+++ b/drivers/i3c/master.c
@@ -267,7 +267,7 @@ static int i3c_device_uevent(struct device *dev, struct kobj_uevent_env *env)
devinfo.dcr, manuf);
return add_uevent_var(env,
- "MODALIAS=i3c:dcr%02Xmanuf%04Xpart%04xext%04x",
+ "MODALIAS=i3c:dcr%02Xmanuf%04Xpart%04Xext%04X",
devinfo.dcr, manuf, part, ext);
}
--
2.24.1
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2020-02-22 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 10:27 [PATCH 0/3] i3c: Address i3c_device_id related issues Boris Brezillon
2020-02-22 10:27 ` Boris Brezillon [this message]
2020-02-22 10:27 ` [PATCH 2/3] i3c: Generate aliases for i3c modules Boris Brezillon
2020-02-26 11:50 ` Boris Brezillon
2020-02-22 10:27 ` [PATCH 3/3] i3c: Simplify i3c_device_match_id() Boris Brezillon
2020-02-26 17:37 ` [PATCH 0/3] i3c: Address i3c_device_id related issues Boris Brezillon
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=20200222102711.1352006-2-boris.brezillon@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=Vitor.Soares@synopsys.com \
--cc=bbrezillon@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgaj@cadence.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).