From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>, jani.nikula@intel.com
Cc: daniel.vetter@ffwll.ch, airlied@gmail.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
jani.nikula@linux.intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
chris@chris-wilson.co.uk, tvrtko.ursulin@intel.com,
davidx.m.ertman@intel.com, bruce.w.allan@intel.com
Subject: Re: [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails
Date: Tue, 06 Jun 2017 13:46:26 -0700 [thread overview]
Message-ID: <1496781986.86439.3.camel@intel.com> (raw)
In-Reply-To: <20170602.141426.713378366601051907.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
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.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-06 20:46 UTC|newest]
Thread overview: 17+ 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 15:08 ` David Miller
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-06-02 18:14 ` David Miller
2017-06-06 20:46 ` Jeff Kirsher [this message]
2017-06-07 1:07 ` [Intel-wired-lan] " Brown, Aaron F
2017-06-20 8:49 ` Daniel Vetter
2017-06-27 19:28 ` Dave Airlie
2017-06-27 20:51 ` Jeff Kirsher
2017-06-28 5:35 ` Daniel Vetter
2017-06-05 5:20 ` Neftin, Sasha
2017-05-31 16:23 ` [PULL] topic/e1000e-fix 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=1496781986.86439.3.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=airlied@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=davem@davemloft.net \
--cc=davidx.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=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 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).