From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Bin Gao <bin.gao@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>,
Yegnesh S Iyer <yegnesh.s.iyer@intel.com>,
Bin Gao <bin.gao@intel.com>
Subject: Re: [PATCH v7] gpio: add Intel WhiskeyCove PMIC GPIO driver
Date: Tue, 13 Sep 2016 17:35:57 +0300 [thread overview]
Message-ID: <CAHp75Vd6X_f7sO0MqjTBgbpWHSNKxiL6iQytmYqTnb=3W8Lz-w@mail.gmail.com> (raw)
In-Reply-To: <20160913133726.GI28311@windriver.com>
On Tue, Sep 13, 2016 at 4:37 PM, Paul Gortmaker
<paul.gortmaker@windriver.com> wrote:
>> > This looks like an invalid address, and ....
>>
>> >> +MODULE_AUTHOR("Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>");
>> >
>> > ...the same here. In fact it sure looks like two names. Anyway I just got a
>> > bounce when I tried to use it...
>>
>> It might be that person is no longer working for Intel, though I think
>> It would be better log message for that.
>
> That might make sense if the driver was old, but it hasn't even hit
> mainline yet -- it is only in linux-next, so it cant be more than a few
> weeks old.
It's already quite off topic, so, I would just say that it is still
valid point. Starting from some version of the series (which takes
couple of months?) Bin Gao did improvements.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2016-09-13 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 21:59 [PATCH v7] gpio: add Intel WhiskeyCove PMIC GPIO driver Bin Gao
2016-08-11 11:30 ` Linus Walleij
2016-09-12 22:37 ` Paul Gortmaker
2016-09-13 7:02 ` Andy Shevchenko
2016-09-13 13:37 ` Paul Gortmaker
2016-09-13 14:35 ` Andy Shevchenko [this message]
2016-09-13 14:46 ` Paul Gortmaker
2016-09-13 15:49 ` Gao, Bin
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='CAHp75Vd6X_f7sO0MqjTBgbpWHSNKxiL6iQytmYqTnb=3W8Lz-w@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=ajay.thomas.david.rajamanickam@intel.com \
--cc=bin.gao@intel.com \
--cc=bin.gao@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=paul.gortmaker@windriver.com \
--cc=yegnesh.s.iyer@intel.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 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.