All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brown, Aaron F" <aaron.f.brown@intel.com>
To: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	David Miller <davem@davemloft.net>,
	"Nikula, Jani" <jani.nikula@intel.com>
Cc: "Ursulin, Tvrtko" <tvrtko.ursulin@intel.com>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
	"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
	"Ertman, David M" <david.m.ertman@intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"airlied@gmail.com" <airlied@gmail.com>
Subject: RE: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails
Date: Wed, 7 Jun 2017 01:07:33 +0000	[thread overview]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B8C61D137@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <1496781986.86439.3.camel@intel.com>

> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@osuosl.org] On Behalf
> Of Jeff Kirsher
> Sent: Tuesday, June 6, 2017 1:46 PM
> To: David Miller <davem@davemloft.net>; Nikula, Jani
> <jani.nikula@intel.com>
> Cc: Ursulin, Tvrtko <tvrtko.ursulin@intel.com>; daniel.vetter@ffwll.ch; intel-
> gfx@lists.freedesktop.org; linux-kernel@vger.kernel.org;
> jani.nikula@linux.intel.com; chris@chris-wilson.co.uk; Ertman, David M
> <david.m.ertman@intel.com>; intel-wired-lan@lists.osuosl.org; dri-
> devel@lists.freedesktop.org; netdev@vger.kernel.org; airlied@gmail.com
> Subject: Re: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo
> e1000e_pm_freeze if __e1000_shutdown fails
> 
> On Fri, 2017-06-02 at 14:14 -0400, David Miller wrote:
> > From: Jani Nikula <jani.nikula@intel.com>
> > Date: Wed, 31 May 2017 18:50:43 +0300
> >
> > > From: Chris Wilson <chris@chris-wilson.co.uk>
> > >
> > > An error during suspend (e100e_pm_suspend),
> >
> >  ...
> > > lead to complete failure:
> >
> >  ...
> > > The unwind failures stems from commit 2800209994f8 ("e1000e:
> > > Refactor PM
> > > flows"), but it may be a later patch that introduced the non-
> > > recoverable
> > > behaviour.
> > >
> > > Fixes: 2800209994f8 ("e1000e: Refactor PM flows")
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99847
> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > > Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > > Cc: Dave Ertman <davidx.m.ertman@intel.com>
> > > Cc: Bruce Allan <bruce.w.allan@intel.com>
> > > Cc: intel-wired-lan@lists.osuosl.org
> > > Cc: netdev@vger.kernel.org
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > [Jani: bikeshed repainted]
> > > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >
> > Jeff, please make sure this gets submitted to me soon.
> 
> Expect it later tonight, just finishing up testing.

Tested-by: Aaron Brown <aaron.f.brown@intel.com>

WARNING: multiple messages have this Message-ID (diff)
From: "Brown, Aaron F" <aaron.f.brown@intel.com>
To: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	David Miller <davem@davemloft.net>,
	"Nikula, Jani" <jani.nikula@intel.com>
Cc: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Ertman, David M" <david.m.ertman@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails
Date: Wed, 7 Jun 2017 01:07:33 +0000	[thread overview]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B8C61D137@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <1496781986.86439.3.camel@intel.com>

> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@osuosl.org] On Behalf
> Of Jeff Kirsher
> Sent: Tuesday, June 6, 2017 1:46 PM
> To: David Miller <davem@davemloft.net>; Nikula, Jani
> <jani.nikula@intel.com>
> Cc: Ursulin, Tvrtko <tvrtko.ursulin@intel.com>; daniel.vetter@ffwll.ch; intel-
> gfx@lists.freedesktop.org; linux-kernel@vger.kernel.org;
> jani.nikula@linux.intel.com; chris@chris-wilson.co.uk; Ertman, David M
> <david.m.ertman@intel.com>; intel-wired-lan@lists.osuosl.org; dri-
> devel@lists.freedesktop.org; netdev@vger.kernel.org; airlied@gmail.com
> Subject: Re: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo
> e1000e_pm_freeze if __e1000_shutdown fails
> 
> On Fri, 2017-06-02 at 14:14 -0400, David Miller wrote:
> > From: Jani Nikula <jani.nikula@intel.com>
> > Date: Wed, 31 May 2017 18:50:43 +0300
> >
> > > From: Chris Wilson <chris@chris-wilson.co.uk>
> > >
> > > An error during suspend (e100e_pm_suspend),
> >
> >  ...
> > > lead to complete failure:
> >
> >  ...
> > > The unwind failures stems from commit 2800209994f8 ("e1000e:
> > > Refactor PM
> > > flows"), but it may be a later patch that introduced the non-
> > > recoverable
> > > behaviour.
> > >
> > > Fixes: 2800209994f8 ("e1000e: Refactor PM flows")
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99847
> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > > Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > > Cc: Dave Ertman <davidx.m.ertman@intel.com>
> > > Cc: Bruce Allan <bruce.w.allan@intel.com>
> > > Cc: intel-wired-lan@lists.osuosl.org
> > > Cc: netdev@vger.kernel.org
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > [Jani: bikeshed repainted]
> > > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >
> > Jeff, please make sure this gets submitted to me soon.
> 
> Expect it later tonight, just finishing up testing.

Tested-by: Aaron Brown <aaron.f.brown@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Brown, Aaron F <aaron.f.brown@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails
Date: Wed, 7 Jun 2017 01:07:33 +0000	[thread overview]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B8C61D137@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <1496781986.86439.3.camel@intel.com>

> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On Behalf
> Of Jeff Kirsher
> Sent: Tuesday, June 6, 2017 1:46 PM
> To: David Miller <davem@davemloft.net>; Nikula, Jani
> <jani.nikula@intel.com>
> Cc: Ursulin, Tvrtko <tvrtko.ursulin@intel.com>; daniel.vetter at ffwll.ch; intel-
> gfx at lists.freedesktop.org; linux-kernel at vger.kernel.org;
> jani.nikula at linux.intel.com; chris at chris-wilson.co.uk; Ertman, David M
> <david.m.ertman@intel.com>; intel-wired-lan at lists.osuosl.org; dri-
> devel at lists.freedesktop.org; netdev at vger.kernel.org; airlied at gmail.com
> Subject: Re: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo
> e1000e_pm_freeze if __e1000_shutdown fails
> 
> On Fri, 2017-06-02 at 14:14 -0400, David Miller wrote:
> > From: Jani Nikula <jani.nikula@intel.com>
> > Date: Wed, 31 May 2017 18:50:43 +0300
> >
> > > From: Chris Wilson <chris@chris-wilson.co.uk>
> > >
> > > An error during suspend (e100e_pm_suspend),
> >
> >  ...
> > > lead to complete failure:
> >
> >  ...
> > > The unwind failures stems from commit 2800209994f8 ("e1000e:
> > > Refactor PM
> > > flows"), but it may be a later patch that introduced the non-
> > > recoverable
> > > behaviour.
> > >
> > > Fixes: 2800209994f8 ("e1000e: Refactor PM flows")
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99847
> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > > Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > > Cc: Dave Ertman <davidx.m.ertman@intel.com>
> > > Cc: Bruce Allan <bruce.w.allan@intel.com>
> > > Cc: intel-wired-lan at lists.osuosl.org
> > > Cc: netdev at vger.kernel.org
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > [Jani: bikeshed repainted]
> > > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >
> > Jeff, please make sure this gets submitted to me soon.
> 
> Expect it later tonight, just finishing up testing.

Tested-by: Aaron Brown <aaron.f.brown@intel.com>

  reply	other threads:[~2017-06-07  1:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 20:15 [PULL] topic/e1000e-fix Daniel Vetter
2017-05-30 22:10 ` David Miller
2017-05-30 23:06   ` Dave Airlie
2017-05-31  5:54     ` Daniel Vetter
2017-05-31  6:10       ` Daniel Vetter
2017-05-31  6:10         ` [Intel-wired-lan] " Daniel Vetter
2017-05-31  6:10         ` Daniel Vetter
2017-05-31 15:08         ` David Miller
2017-05-31 15:08           ` [Intel-wired-lan] " David Miller
2017-05-31 15:50           ` Jani Nikula
2017-05-31 15:50             ` [Intel-wired-lan] " Jani Nikula
2017-05-31 15:50             ` Jani Nikula
2017-05-31 15:50             ` [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails Jani Nikula
2017-05-31 15:50               ` [Intel-wired-lan] " Jani Nikula
2017-05-31 15:50               ` Jani Nikula
2017-06-02 18:14               ` David Miller
2017-06-02 18:14                 ` [Intel-wired-lan] " David Miller
2017-06-02 18:14                 ` David Miller
2017-06-06 20:46                 ` Jeff Kirsher
2017-06-06 20:46                   ` [Intel-wired-lan] " Jeff Kirsher
2017-06-07  1:07                   ` Brown, Aaron F [this message]
2017-06-07  1:07                     ` Brown, Aaron F
2017-06-07  1:07                     ` Brown, Aaron F
2017-06-20  8:49                     ` Daniel Vetter
2017-06-20  8:49                       ` Daniel Vetter
2017-06-20  8:49                       ` Daniel Vetter
2017-06-27 19:28                       ` Dave Airlie
2017-06-27 19:28                         ` Dave Airlie
2017-06-27 19:28                         ` Dave Airlie
2017-06-27 20:51                         ` Jeff Kirsher
2017-06-27 20:51                           ` Jeff Kirsher
2017-06-27 20:51                           ` Jeff Kirsher
2017-06-27 20:51                           ` Jeff Kirsher
2017-06-28  5:35                           ` Daniel Vetter
2017-06-28  5:35                             ` Daniel Vetter
2017-06-28  5:35                             ` Daniel Vetter
2017-06-05  5:20               ` Neftin, Sasha
2017-06-05  5:20                 ` Neftin, Sasha
2017-06-05  5:20                 ` Neftin, Sasha
2017-05-31 16:23           ` [PULL] topic/e1000e-fix Daniel Vetter
2017-05-31 16:23             ` [Intel-wired-lan] " Daniel Vetter
2017-05-31 16:23             ` Daniel Vetter

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=309B89C4C689E141A5FF6A0C5FB2118B8C61D137@ORSMSX101.amr.corp.intel.com \
    --to=aaron.f.brown@intel.com \
    --cc=airlied@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=davem@davemloft.net \
    --cc=david.m.ertman@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jani.nikula@intel.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tvrtko.ursulin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.