All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Gardner <tim.gardner@canonical.com>
To: romieu@fr.zoreil.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>
Subject: r8169 stable updates
Date: Thu, 29 Apr 2010 13:48:02 +0100	[thread overview]
Message-ID: <4BD98002.6030308@canonical.com> (raw)

Francois,

If not already proposed, I think these commits are appropriate for 
stable updates. Do you agree? They apply cleanly to 2.6.32 and will 
likely fix the symptoms of this bug: 
http://bugs.launchpad.net/bugs/562742 (still in test).

4c020a961a812ffae9846b917304cea504c3a733 r8169: use correct barrier 
between cacheable and non-cacheable memory

78f1cd02457252e1ffbc6caa44a17424a45286b8 r8169: fix broken register writes

908ba2bfd22253f26fa910cd855e4ccffb1467d0 r8169: more broken register 
writes workaround

rtg
-- 
Tim Gardner tim.gardner@canonical.com

             reply	other threads:[~2010-04-30 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 12:48 Tim Gardner [this message]
2010-04-29 21:57 ` r8169 stable updates Francois Romieu
2010-05-07 22:21 ` [stable] " Greg KH

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=4BD98002.6030308@canonical.com \
    --to=tim.gardner@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=stable@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 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.