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
Subject: Re: [PATCH 2/3] i3c: Generate aliases for i3c modules
Date: Wed, 26 Feb 2020 12:50:04 +0100 [thread overview]
Message-ID: <20200226125004.39748c1d@collabora.com> (raw)
In-Reply-To: <20200222102711.1352006-3-boris.brezillon@collabora.com>
On Sat, 22 Feb 2020 11:27:10 +0100
Boris Brezillon <boris.brezillon@collabora.com> wrote:
> +static int do_i3c_entry(const char *filename, void *symval,
> + char *alias)
> +{
> + DEF_FIELD(symval, i3c_device_id, match_flags);
> + DEF_FIELD(symval, i3c_device_id, dcr);
> + DEF_FIELD(symval, i3c_device_id, manuf_id);
> + DEF_FIELD(symval, i3c_device_id, part_id);
> + DEF_FIELD(symval, i3c_device_id, extra_info);
> +
> + strcpy(alias, "i3c:");
> + ADD(alias, "dcr", match_flags & I3C_MATCH_DCR, dcr);
> + ADD(alias, "manuf", match_flags & I3C_MATCH_MANUF, dcr);
^manuf_id
> + ADD(alias, "part", match_flags & I3C_MATCH_PART, dcr);
^part_id
> + ADD(alias, "ext", match_flags & I3C_MATCH_EXTRA_INFO, dcr);
^extra_info
next prev parent reply other threads:[~2020-02-26 11:50 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 ` [PATCH 1/3] i3c: Fix MODALIAS uevents Boris Brezillon
2020-02-22 10:27 ` [PATCH 2/3] i3c: Generate aliases for i3c modules Boris Brezillon
2020-02-26 11:50 ` Boris Brezillon [this message]
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=20200226125004.39748c1d@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).