public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [samsung:devfreq-for-next 4/4] drivers/devfreq/devfreq.c:639:16: error: invalid storage class fo
Date: Fri, 05 Oct 2012 01:09:59 +0000	[thread overview]
Message-ID: <20121005010959.GA7437@localhost> (raw)
In-Reply-To: <20121005010649.GA6635@localhost>

On Fri, Oct 05, 2012 at 09:06:49AM +0800, Fengguang Wu wrote:
> Hi MyungJoo,
> 
> FYI, kernel build failed on
> 
> tree:   git://git.infradead.org/users/kmpark/linux-samsung devfreq-for-next
> head:   6f2fe082f51cf10ea622e21bff4f5d313decee36
> commit: 6f2fe082f51cf10ea622e21bff4f5d313decee36 [4/4] PM / devfreq: add global PM QoS support
> config: x86_64-allyesconfig
> 
> Note: the HEAD commit builds fine. It only hurts bisectibility.

That "Note" is obviously wrong. Sorry, it should be a bug in the build system.

Thanks,
Fengguang

      reply	other threads:[~2012-10-05  1:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05  1:06 [samsung:devfreq-for-next 4/4] drivers/devfreq/devfreq.c:639:16: error: invalid storage class for fu Fengguang Wu
2012-10-05  1:09 ` Fengguang Wu [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=20121005010959.GA7437@localhost \
    --to=fengguang.wu@intel.com \
    --cc=kernel-janitors@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