From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
linux-arm-kernel@lists.infradead.org,
Andrey Smirnov <andrew.smirnov@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Oleksij Rempel <o.rempel@pengutronix.de>,
linux-i2c@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>, Chris Healy <cphealy@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [PATCH v1] MAINTAINERS: i2c-imx: take over maintainership
Date: Wed, 14 Aug 2019 13:33:44 +0200 [thread overview]
Message-ID: <20190814113344.5j7zh37nm36rlagr@pengutronix.de> (raw)
In-Reply-To: <20190814100224.GE1511@ninjato>
On Wed, Aug 14, 2019 at 12:02:25PM +0200, Wolfram Sang wrote:
>
> > Even without this patch the generic "ARM/FREESCALE IMX / MXC ARM
> > ARCHITECTURE" entry matches the i2c-imx driver.
>
> It matches, but it didn't work well, I am afraid.
I didn't intend to imply it worked well. Just thought it was sensible to
point out that even with the newly added entry in MAINTAINERS the old
entry still matches.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-14 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 5:08 [PATCH v1] MAINTAINERS: i2c-imx: take over maintainership Oleksij Rempel
2019-08-12 6:48 ` Uwe Kleine-König
2019-08-14 10:02 ` Wolfram Sang
2019-08-14 11:33 ` Uwe Kleine-König [this message]
2019-08-14 9:54 ` 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=20190814113344.5j7zh37nm36rlagr@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux@armlinux.org.uk \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).