From: Wolfram Sang <wsa@the-dreams.de>
To: Aisheng Dong <aisheng.dong@nxp.com>
Cc: Anson Huang <anson.huang@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"eha@deif.com" <eha@deif.com>,
"linux@rempel-privat.de" <linux@rempel-privat.de>,
"mojha@codeaurora.org" <mojha@codeaurora.org>,
Laurentiu Tudor <laurentiu.tudor@nxp.com>,
"peda@axentia.se" <peda@axentia.se>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH] i2c: imx: correct the method of getting private data in notifier_call
Date: Tue, 23 Apr 2019 23:22:48 +0200 [thread overview]
Message-ID: <20190423212248.GD5659@kunai> (raw)
In-Reply-To: <AM0PR04MB42110D893D07DFECFE167F5580250@AM0PR04MB4211.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 234 bytes --]
Hey Dong Aisheng,
> Besides above comments:
>
> Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
Are you maybe interested in maintaining this driver? We are seriously
needing one with experience.
Thanks,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-23 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 1:59 [PATCH] i2c: imx: correct the method of getting private data in notifier_call Anson Huang
2019-04-17 3:13 ` Aisheng Dong
2019-04-17 3:17 ` Aisheng Dong
2019-04-23 21:22 ` Wolfram Sang [this message]
2019-04-17 3:18 ` Anson Huang
2019-04-23 21:21 ` Wolfram Sang
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=20190423212248.GD5659@kunai \
--to=wsa@the-dreams.de \
--cc=aisheng.dong@nxp.com \
--cc=anson.huang@nxp.com \
--cc=eha@deif.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=laurentiu.tudor@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mojha@codeaurora.org \
--cc=peda@axentia.se \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa+renesas@sang-engineering.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).