netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: markgross@thegnar.org
Cc: mgross@linux.intel.com, Valdis.Kletnieks@vt.eu,
	e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org, akpm@linux-foundation.org,
	davem@davemloft.net
Subject: Re: [patch] pm_qos update fixing mmotm 2010-05-11 -dies in pm_qos_update_request()
Date: Mon, 17 May 2010 23:58:00 +0200	[thread overview]
Message-ID: <201005172358.00076.rjw@sisk.pl> (raw)
In-Reply-To: <20100517001241.GA2962@thegnar.org>

On Monday 17 May 2010, mgross wrote:
> On Mon, May 17, 2010 at 12:21:25AM +0200, Rafael J. Wysocki wrote:
> > On Saturday 15 May 2010, mgross wrote:
> > > On Sat, May 15, 2010 at 09:38:47PM +0200, Rafael J. Wysocki wrote:
> > > > On Saturday 15 May 2010, mgross wrote:
> > > > > I apologize for the goofy email address.  
> > > > > 
> > > > > The following is a fix for the crash reported by Valdis.
> > > > > 
> > > > > The problem was that the original pm_qos silently fails when a request
> > > > > update is passed to a parameter that has not been added to the list
> > > > > yet.  It seems that the e1000e is doing this.  This update restores this
> > > > > behavior.
> > > > > 
> > > > > I need to think about how to better handle such abuse, but for now this
> > > > > restores the original behavior.
> > > > 
> > > > Can you please post a signed-off incremental patch against
> > > > 
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-2.6.git for-llinus
> > > > 
> > > > that contains your original PM QOS update?
> > > 
> > > No problem:
> > >
> > > Signed-off-by: markgross <markgross@thegnar.org>
> > 
> > Thanks!  Do you want to use this address for the sign-off or the Intel one?
> 
> I guess so.  Ever since switching groups within intel last summer my
> mgross@linux.intel.com address isn't checked as often as this one. 
> 
> The other option is to use my outlook email (mark.gross@intel.com), but
> I really hate posting from outlook.  Besides, doing upstream kernel
> stuff isn't my day job any more so using markgross@thegnar.org  makes
> sense to me.

Good.  Patch applied to suspend-2.6/for-linus.

Thanks,
Rafael

------------------------------------------------------------------------------

_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

      reply	other threads:[~2010-05-17 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15  2:19 [patch] pm_qos update fixing mmotm 2010-05-11 -dies in pm_qos_update_request() mgross
2010-05-15 19:38 ` Rafael J. Wysocki
2010-05-15 21:42   ` mgross
2010-05-16 22:21     ` Rafael J. Wysocki
2010-05-17  0:12       ` mgross
2010-05-17 21:58         ` Rafael J. Wysocki [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=201005172358.00076.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=Valdis.Kletnieks@vt.eu \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=markgross@thegnar.org \
    --cc=mgross@linux.intel.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).