From: "Heasley, Seth" <seth.heasley-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Brown,
Bill E" <bill.e.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: RE: i2c-ismt driver maintenance
Date: Fri, 8 Feb 2013 15:43:16 +0000 [thread overview]
Message-ID: <DEC3922D1904474A8862C7BFF516EA9A59B4B84B@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <20130208121518.GA8771-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
>> Who is going to maintain the i2c-ismt driver? If any of you want to do
>> it, please send a patch adding an entry to the MAINTAINERS file. If
>> not, I can do it and add i2c-ismt to the already long list of SMBus
>> controller drivers I maintain.
>>
>Seth, why don't we both put our names on it, until such time as Bill comes
>back from sabbatical, then he can take it over? Sound good to you?
>Neil
Since I'll be submitting patches for future products, I'd definitely want someone else on the list to review them. So I guess this would work.
-Seth
next prev parent reply other threads:[~2013-02-08 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 9:57 i2c-ismt driver maintenance Jean Delvare
[not found] ` <20130208105756.35d00bae-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2013-02-08 12:15 ` Neil Horman
[not found] ` <20130208121518.GA8771-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2013-02-08 15:43 ` Heasley, Seth [this message]
2013-02-08 15:55 ` [PATCH] i2c-ismt: Add Seth and Myself as maintainers Neil Horman
[not found] ` <1360338922-10812-1-git-send-email-nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2013-02-08 16:09 ` Jean Delvare
2013-02-08 18:27 ` [PATCH v2] " Neil Horman
[not found] ` <1360348061-13153-1-git-send-email-nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2013-02-10 10:10 ` Jean Delvare
2013-02-10 16:59 ` [PATCH v3] " Neil Horman
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=DEC3922D1904474A8862C7BFF516EA9A59B4B84B@ORSMSX101.amr.corp.intel.com \
--to=seth.heasley-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=bill.e.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.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.