linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Eduardo Valentin <edubezval@gmail.com>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Dirk Behme <dirk.behme@de.bosch.com>
Subject: Re: [Thermal] Need confirmation for the pending thermal soc patches
Date: Wed, 07 Sep 2016 08:25:49 +0800	[thread overview]
Message-ID: <1473207949.2307.1.camel@intel.com> (raw)
In-Reply-To: <CAMuHMdVxCyy+ULdnzWTBFuCrP4E77H7JxS25QL_RSeOgtV5bVQ@mail.gmail.com>

On 二, 2016-09-06 at 12:13 +0200, Geert Uytterhoeven wrote:
> Hi Eduardo,
> 
> On Mon, Sep 5, 2016 at 3:16 PM, Eduardo Valentin <edubezval@gmail.com
> > wrote:
> > 
> > On Sun, Aug 21, 2016 at 10:09:00PM +0800, Zhang Rui wrote:
> > > 
> > > As Eduardo is quite busy recently, I will take all the thermal
> > > soc
> > > driver changes this time.
> > Thanks for helping me out. I am slowing coming back to upstream
> > activities. I have refreshed my branches, removing the rework and
> > locking patches works out of the integration branches so we do not
> > have
> > merge conflicts or further delays on outstanding patches.
> > 
> > > 
> > > Currently, I have cherry picked all the patches that Eduardo has
> > > already applied in thermal-soc tree and reviewed all the pending
> > Great! This makes things easier for me.
> > 
> > > 
> > > patches in patchwork. Now, there are four patches queued for next
> > > -rc (
> > > https://git.kernel.org/cgit/linux/kernel/git/rzhang/linux.git/log
> > > /?h=fo
> > > r-rc),
> > I checked this branch. Can you please cherry-pick the following
> > patch
> > for rc:
> > https://git.kernel.org/cgit/linux/kernel/git/evalenti/linux-soc-
> > thermal.git/commit/?h=linus&id=4ba16f1256bd13efa2f3179ff1f4ab16a4ad
> > 3c7f

> That patch is indeed missing.
> 
> While preparing today's renesas-drivers release, I noticed it had
> disappeared
> from thermal-soc/next. Then I found your email...
> 
> Thanks for re-applying it!
> 

Applied and queued for next -rc.

thanks,
rui

> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linu
> x-m68k.org
> 
> In personal conversations with technical people, I call myself a
> hacker. But
> when I'm talking to journalists I just say "programmer" or something
> like that.
>                                 -- Linus Torvalds
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2016-09-07  0:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 14:09 [Thermal] Need confirmation for the pending thermal soc patches Zhang Rui
2016-09-05 13:16 ` Eduardo Valentin
2016-09-06 10:13   ` Geert Uytterhoeven
2016-09-07  0:25     ` Zhang Rui [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=1473207949.2307.1.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=edubezval@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@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).