linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei Ni <wni@nvidia.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: thierry.reding@gmail.com, rui.zhang@intel.com,
	MLongnecker@nvidia.com, swarren@wwwdotorg.org,
	mikko.perttunen@kapsi.fi, linux-tegra@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm
Date: Tue, 29 Mar 2016 18:19:44 +0800	[thread overview]
Message-ID: <56FA56C0.4060000@nvidia.com> (raw)
In-Reply-To: <56FA0B45.70404@nvidia.com>



On 2016年03月29日 12:57, Wei Ni wrote:
> 
> 
> On 2016年03月29日 11:04, Eduardo Valentin wrote:
>> On Fri, Mar 25, 2016 at 01:37:17PM +0800, Wei Ni wrote:
>>> Hi, Eduardo
>>> Will you take this series, it seems no more comments.
>>
>> Yeah, I am taking a look at it. Something is fishy about it. Patch 04
>> does not apply cleanly. Also, why did you split the patches into two
>> email threads, one which is 1-4 and another one is 5-14?
> 
> Sorry, what do you mean "split the patches into two email threads"? And what's
> the 1-4 and 5-14?
> I think I didn't split my patches into two email thread.

I think I knew what's your mean.
When I use "git send-email --to=xxx *.patch" to send patches, I hit " 4.4.2
Message submission rate for this client has exceeded the configured limit".
So I split them to send.
And I didn't realized it will cause problems before I sending out V9 series, so
I sent V9 patches one by one, they appear as individual emails on the mailing
list, not as a thread.
I will check my email system and resend them.

Thanks.
Wei.

> 
> Thanks.
> Wei.
> 
>>
>> I have ammended patch 04 at my side, but you need to validate your
>> series is one piece (please check my tree and linux-next).
>>
>> BR,
>>
>> Eduardo Valentin
>>
>>>

      reply	other threads:[~2016-03-29 10:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16  8:55 [PATCH V8 00/14] Add T210 support in Tegra soctherm Wei Ni
2016-03-16  8:55 ` [PATCH V8 02/14] thermal: tegra: combine sensor group-related data Wei Ni
2016-03-16  8:56 ` [PATCH V8 03/14] thermal: tegra: get rid of PDIV/HOTSPOT hack Wei Ni
     [not found] ` <1458118571-29717-1-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-16  8:55   ` [PATCH V8 01/14] thermal: tegra: move tegra thermal files into tegra directory Wei Ni
2016-03-16  8:56   ` [PATCH V8 04/14] thermal: tegra: split tegra_soctherm driver Wei Ni
2016-03-25  5:37   ` [PATCH V8 00/14] Add T210 support in Tegra soctherm Wei Ni
2016-03-28 13:38     ` Eduardo Valentin
     [not found]     ` <56F4CE8D.5020108-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-29  3:04       ` Eduardo Valentin
2016-03-29  3:29         ` Eduardo Valentin
     [not found]           ` <20160329032953.GA24089-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-03-29  4:22             ` Wei Ni
2016-03-29  4:57         ` Wei Ni
2016-03-29 10:19           ` Wei Ni [this message]

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=56FA56C0.4060000@nvidia.com \
    --to=wni@nvidia.com \
    --cc=MLongnecker@nvidia.com \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mikko.perttunen@kapsi.fi \
    --cc=rui.zhang@intel.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.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).