mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org
Subject: Re: [LKP] [drm/i915] WARNING: CPU: 3 PID: 248 at drivers/gpu/drm/i915/intel_pm.c:6427 check_power_well_state+0x60/0x90 [i915]()
Date: Thu, 31 Jul 2014 13:09:33 +0800	[thread overview]
Message-ID: <20140731050933.GB9386@aaronlu.sh.intel.com> (raw)
In-Reply-To: <CAKMK7uHAH5is3+CGOxTimxjx2x1auYf4gXAzWjkuTdB2mRkk-Q@mail.gmail.com>

On Wed, Jul 30, 2014 at 11:40:05AM +0200, Daniel Vetter wrote:
> On Wed, Jul 30, 2014 at 4:20 AM, Aaron Lu <aaron.lu@intel.com> wrote:
> > On 07/29/2014 07:10 PM, Daniel Vetter wrote:
> >> On Tue, Jul 29, 2014 at 12:14 PM, Ville Syrjälä
> >> <ville.syrjala@linux.intel.com> wrote:
> >>> On Tue, Jul 29, 2014 at 10:43:02AM +0800, Aaron Lu wrote:
> >>>> FYI, we noticed the below changes on
> >>>>
> >>>> git://people.freedesktop.org/~danvet/drm colder-fusion
> >>>
> >>> Does it happen on -nightly too?
> >>
> >> git://anongit.freedesktop.org/drm-intel
> >
> > With this git tree, do we still need to watch the old one? Or they serve
> > different purpose?
> 
> The old one is just my private repo, never contained official
> branches. The one I've given is the official drm-intel git for
> upstream.

Thanks for the clarification, we have removed your private repo.

Regards,
Aaron

  reply	other threads:[~2014-07-31  5:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53d70753.0iBGqYd97TVbYboG%fengguang.wu@intel.com>
2014-07-29  2:43 ` Aaron Lu
2014-07-29 10:14   ` Ville Syrjälä
2014-07-29 11:10     ` Daniel Vetter
2014-07-30  2:20       ` Aaron Lu
2014-07-30  9:40         ` Daniel Vetter
2014-07-31  5:09           ` Aaron Lu [this message]
2014-07-31  2:19       ` Aaron Lu

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=20140731050933.GB9386@aaronlu.sh.intel.com \
    --to=aaron.lu@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ville.syrjala@linux.intel.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

Powered by JetHome