From: Steve Twiss <stwiss.opensource@diasemi.com>
To: Joe Perches <joe@perches.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Support Opensource <Support.Opensource@diasemi.com>
Subject: RE: MAINTAINERS without commits in the last 3 years
Date: Thu, 25 Aug 2016 07:29:57 +0000 [thread overview]
Message-ID: <6ED8E3B22081A4459DAC7699F3695FB70173DD2C06@SW-EX-MBX02.diasemi.com> (raw)
In-Reply-To: <1472081625.3746.217.camel@perches.com>
Hi Joe,
The address "support.opensource@diasemi.com" works. Thanks.
On 25 August 2016 00:34 Joe Perches wrote:
> Many email addresses in MAINTAINERS no longer work so many
> sections in MAINTAINERS could likely be considered either
> obsolete or unmaintained.
[...]
> The email addresses below are also bcc'd here to see what bounces.
> The list of the bounces will be collected.
>
> Thoughts?
>
[...]
> support.opensource@diasemi.com
The support.opensource e-mail address is an alias contact group that sends to all kernel developers
at Dialog Semiconductor.
There is no way for that address to submit content to the kernel, we do that individually through
our personal e-mail (for accountability reasons), but when that address is used externally to contact
Dialog about our drivers, it gets translated and sent to all current Dialog kernel driver developers.
That method has advantages for us: all developers gets the message; it ensures somebody will pick up
the query; we can alter the internal developer inbox addresses and alter the list of developers internally ..
and we only need a single e-mail address in the kernel MAINTAINERS list.
Regards,
Steve
next prev parent reply other threads:[~2016-08-25 7:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 23:33 MAINTAINERS without commits in the last 3 years Joe Perches
[not found] ` <CA+i2_Ddvg9a0S23ywJtXQbLuq3JLJF9poH=n_G1+9uWWVPZwOg@mail.gmail.com>
2016-08-25 0:24 ` Joe Perches
[not found] ` <CAHrUA37xh-6GLkTAM75w8v550rR8n2Ayycjy9FNofv3K+=QoVQ@mail.gmail.com>
2016-08-25 2:09 ` Joe Perches
2016-08-25 3:26 ` Alexander Graf
2016-08-25 7:01 ` Ali Akcaagac
2016-08-25 7:29 ` Steve Twiss [this message]
2016-08-25 10:12 ` Mauro Carvalho Chehab
2016-08-25 16:12 ` David Carroll
2016-08-25 20:46 ` Steven French
2016-08-25 20:58 ` Greg KH
2016-08-26 0:33 ` Joe Perches
2016-08-26 12:59 ` Shuah Khan
2016-08-26 16:56 ` Florian Fainelli
2016-08-26 17:09 ` Joe Perches
2016-08-26 19:34 ` Jason Baron
2016-08-26 19:50 ` Joe Perches
2016-08-26 20:05 ` Borislav Petkov
2016-08-26 20:17 ` Luck, Tony
2016-09-01 12:58 ` Borislav Petkov
2016-09-01 16:02 ` Joe Perches
2016-09-02 5:26 ` Borislav Petkov
[not found] ` <CACwGpODqLAjQxgw=EdtWCKhFywy9btv9Ka6XG8YXbzKEBFPzEg@mail.gmail.com>
2016-08-28 2:40 ` Joe Perches
2016-08-30 15:19 ` Anders Larsen
2016-08-30 15:35 ` Joe Perches
2016-08-24 23:33 Joe Perches
2016-08-25 10:00 Tigran Aivazian
2016-08-25 10:09 ` Joe Perches
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=6ED8E3B22081A4459DAC7699F3695FB70173DD2C06@SW-EX-MBX02.diasemi.com \
--to=stwiss.opensource@diasemi.com \
--cc=Support.Opensource@diasemi.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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 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.