From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>,
Ian Ray <ian.ray@ge.com>, Nandor Han <nandor.han@vaisala.com>
Cc: "geert+renesas@glider.be" <geert+renesas@glider.be>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/2] Add definition for GPIO direction
Date: Thu, 7 Nov 2019 13:08:59 +0100 [thread overview]
Message-ID: <20191107120859.zoml7cmxbtaetjsk@earth.universe> (raw)
In-Reply-To: <2ca76ecb58b9e6377925d6790ff4f7722604f57b.camel@fi.rohmeurope.com>
[-- Attachment #1.1: Type: text/plain, Size: 841 bytes --]
Hi,
On Thu, Nov 07, 2019 at 08:52:11AM +0000, Vaittinen, Matti wrote:
> That reminded me.. I got 'unknown recipient' replies
> <nandor.han@ge.com>: 550 5.1.1 No such user - pp
> <semi.malinen@ge.com>: 550 5.1.1 No such user - pp
>
> from both Semi and Nandor - who seem to be the only maintainers listed
> for XRA1403 GPIO EXPANDER in MAINTAINERS.
>
> XRA1403 GPIO EXPANDER
> M: Nandor Han <nandor.han@ge.com>
> M: Semi Malinen <semi.malinen@ge.com>
> L: linux-gpio@vger.kernel.org
> S: Maintained
> F: drivers/gpio/gpio-xra1403.c
> F: Documentation/devicetree/bindings/gpio/gpio-xra1403.txt
>
> Anyone knows new mail addresses or perhaps the separate entry
> for XRA1403 should be removed?
+cc new mail address from Nandor Han
+cc Ian Ray with valid GE mail address
-- Sebastian
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-11-07 12:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 8:51 [PATCH v2 0/2] Add definition for GPIO direction Matti Vaittinen
2019-11-06 8:51 ` [PATCH v2 1/2] gpio: " Matti Vaittinen
2019-11-07 8:20 ` Linus Walleij
2019-11-06 8:54 ` [PATCH v2 2/2] gpio: Use new GPIO_LINE_DIRECTION Matti Vaittinen
2019-11-06 14:22 ` Andy Shevchenko
2019-11-06 14:43 ` William Breathitt Gray
2019-11-06 17:35 ` Kuppuswamy Sathyanarayanan
2019-11-06 12:08 ` [PATCH v2 0/2] Add definition for GPIO direction Sebastian Reichel
2019-11-06 12:25 ` Vaittinen, Matti
2019-11-06 14:24 ` andriy.shevchenko
2019-11-07 8:26 ` Linus Walleij
2019-11-07 8:32 ` Geert Uytterhoeven
2019-11-07 8:52 ` Vaittinen, Matti
2019-11-07 12:08 ` Sebastian Reichel [this message]
2019-11-08 7:46 ` Nandor Han
2019-11-07 8:52 ` andriy.shevchenko
2019-11-07 8:22 ` Linus Walleij
2019-11-06 14:39 ` William Breathitt Gray
2019-11-06 17:28 ` Vaittinen, Matti
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=20191107120859.zoml7cmxbtaetjsk@earth.universe \
--to=sebastian.reichel@collabora.com \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=andrew@aj.id.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=geert+renesas@glider.be \
--cc=ian.ray@ge.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=nandor.han@vaisala.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).