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: linux-kernel@vger.kernel.org, Boris Brezillon <boris.brezillon@collabora.com> Subject: [PATCH 0/3] i3c: Address i3c_device_id related issues Date: Sat, 22 Feb 2020 11:27:08 +0100 [thread overview] Message-ID: <20200222102711.1352006-1-boris.brezillon@collabora.com> (raw) Hello, When the I3C subsystem was introduced part of the modalias generation logic was missing (modalias generation based on i3c_device_id tables). This patch series addresses that limitation and simplifies our match function along the way. Regards, Boris Boris Brezillon (3): i3c: Fix MODALIAS uevents i3c: Generate aliases for i3c modules i3c: Simplify i3c_device_match_id() drivers/i3c/device.c | 50 ++++++++++++++----------------- drivers/i3c/master.c | 2 +- scripts/mod/devicetable-offsets.c | 7 +++++ scripts/mod/file2alias.c | 19 ++++++++++++ 4 files changed, 49 insertions(+), 29 deletions(-) -- 2.24.1
WARNING: multiple messages have this Message-ID (diff)
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 0/3] i3c: Address i3c_device_id related issues Date: Sat, 22 Feb 2020 11:27:08 +0100 [thread overview] Message-ID: <20200222102711.1352006-1-boris.brezillon@collabora.com> (raw) Hello, When the I3C subsystem was introduced part of the modalias generation logic was missing (modalias generation based on i3c_device_id tables). This patch series addresses that limitation and simplifies our match function along the way. Regards, Boris Boris Brezillon (3): i3c: Fix MODALIAS uevents i3c: Generate aliases for i3c modules i3c: Simplify i3c_device_match_id() drivers/i3c/device.c | 50 ++++++++++++++----------------- drivers/i3c/master.c | 2 +- scripts/mod/devicetable-offsets.c | 7 +++++ scripts/mod/file2alias.c | 19 ++++++++++++ 4 files changed, 49 insertions(+), 29 deletions(-) -- 2.24.1 _______________________________________________ linux-i3c mailing list linux-i3c@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2020-02-22 10:27 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-22 10:27 Boris Brezillon [this message] 2020-02-22 10:27 ` [PATCH 0/3] i3c: Address i3c_device_id related issues Boris Brezillon 2020-02-22 10:27 ` [PATCH 1/3] i3c: Fix MODALIAS uevents Boris Brezillon 2020-02-22 10:27 ` Boris Brezillon 2020-02-22 10:27 ` [PATCH 2/3] i3c: Generate aliases for i3c modules Boris Brezillon 2020-02-22 10:27 ` Boris Brezillon 2020-02-26 11:50 ` 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-22 10:27 ` Boris Brezillon 2020-02-26 17:37 ` [PATCH 0/3] i3c: Address i3c_device_id related issues Boris Brezillon 2020-02-26 17:37 ` 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-1-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: linkBe 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.