public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	"Li, Philip" <philip.li@intel.com>
Subject: Re: [GIT PULL] Thermal management updates for v4.17-rc1
Date: Thu, 12 Apr 2018 13:08:31 +0800	[thread overview]
Message-ID: <1523509711.16235.25.camel@intel.com> (raw)
In-Reply-To: <CA+55aFzqJ2PfUnkVJ6A-8WRQTciWb8j+25r41JLCvz7h0QEJiA@mail.gmail.com>

Hi, Linus,

On 三, 2018-04-11 at 17:01 -0700, Linus Torvalds wrote:
> On Wed, Apr 11, 2018 at 1:41 AM, Zhang Rui <rui.zhang@intel.com>
> wrote:
> > 
> > 
> > Please pull from
> >   git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git
> > next
> Pulled, and then immediately unpulled again.
> 
> The code causes new compiler warnings, and the warnings are valid.
> 
> If people don't care enough about their code to even check the
> warnings, I'm not going to waste one second pulling the resulting
> garbage. It's that simple.
> 

I'm really sorry for this.
could you please illustrate me what the kconfig & warning is?
I didn't
get such warnings from 0-day.

thanks,
rui

  reply	other threads:[~2018-04-12  5:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  8:41 [GIT PULL] Thermal management updates for v4.17-rc1 Zhang Rui
2018-04-12  0:01 ` Linus Torvalds
2018-04-12  5:08   ` Zhang Rui [this message]
2018-04-12 16:55     ` Linus Torvalds
2018-04-12 17:42       ` Daniel Lezcano
2018-04-13  4:08       ` Eduardo Valentin
2018-04-13  5:29         ` Zhang Rui
2018-04-13  5:39         ` Zhang Rui
2018-04-13  8:55           ` Bartlomiej Zolnierkiewicz
2018-04-13  9:00             ` Daniel Lezcano
2018-04-13  9:08               ` Bartlomiej Zolnierkiewicz
2018-04-13  9:19                 ` Daniel Lezcano
2018-04-13  9:28                   ` Bartlomiej Zolnierkiewicz
2018-04-13 10:30                     ` Daniel Lezcano
2018-04-13 10:41                       ` Bartlomiej Zolnierkiewicz
2018-04-13 11:00                         ` [PATCH] thermal/drivers/exynos_tmu: Fix warnings in temp_to_code / code_to_temp Daniel Lezcano
2018-04-13 11:08                           ` Bartlomiej Zolnierkiewicz
2018-04-13 11:10                         ` [GIT PULL] Thermal management updates for v4.17-rc1 Daniel Lezcano
2018-04-13 11:12                         ` Bartlomiej Zolnierkiewicz
2018-04-13 11:21                           ` Bartlomiej Zolnierkiewicz
2018-04-13 10:08           ` Eduardo Valentin
2018-04-13 10:25             ` Eduardo Valentin
2018-04-13 10:27             ` Bartlomiej Zolnierkiewicz
2018-04-15  8:51               ` Eduardo Valentin
2018-04-13  8:50         ` Bartlomiej Zolnierkiewicz

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=1523509711.16235.25.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=philip.li@intel.com \
    --cc=torvalds@linux-foundation.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