linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	Amit Kucheria <amit.kucheria@verdurent.com>,
	"eduval@amazon.com" <eduval@amazon.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: thermal: Eduardo's email is bouncing
Date: Wed, 04 Dec 2019 14:26:01 +0800	[thread overview]
Message-ID: <dc1bc99ecfc6095d54a43cac1523984f4034dd72.camel@intel.com> (raw)
In-Reply-To: <c4c94fc3-2b57-188a-1b91-c0889e593049@gmail.com>

On Tue, 2019-12-03 at 20:56 -0800, Florian Fainelli wrote:
> 
> On 11/26/2019 7:34 AM, Zhang, Rui wrote:
> > Let's try Eduardo' Amazon email account before applying this one.
> 
> How much longer do you want to give Eduardo a chance to respond?
> 
> I would like to draw your attention towards the response time of the
> thermal subsystem maintainers for a subsystem that is say medium in
> traffic.
> 
> You guys need to step up your game and give some feedback within days
> and not weeks of patches being submitted, especially if this is after
> 2
> or 3 requests to get feedback.
> 
> If all of you are busy which is completely understandable then maybe
> it
> is time to seek help from someone else (Daniel?) who gives timely
> feedback to patches submissions.
> 

First of all, I don't want to add any new patch during the merge
window. And this patch will be applied and pushed once after -rc1
released.
Plus, I've already synced with Daniel, in private email though, and I
will send an incremental patch to add Daniel as the co-maintainer of
the thermal subsystem.

thanks,
rui



  reply	other threads:[~2019-12-04  6:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 15:43 [PATCH] MAINTAINERS: thermal: Eduardo's email is bouncing Florian Fainelli
2019-11-25  9:57 ` Amit Kucheria
2019-11-26  5:29   ` Zhang Rui
2019-11-26 15:34     ` Zhang, Rui
2019-12-04  4:56       ` Florian Fainelli
2019-12-04  6:26         ` Zhang Rui [this message]
2019-12-05 11:52 ` Zhang Rui

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=dc1bc99ecfc6095d54a43cac1523984f4034dd72.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=eduval@amazon.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@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 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).