All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Erwan Velu <erwanaliasr1@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Opportunity to backport pch_gbe patches to stable 3.2.x
Date: Wed, 19 Sep 2012 21:49:05 +0100	[thread overview]
Message-ID: <20120919204905.GE29217@decadent.org.uk> (raw)
In-Reply-To: <505A11E2.8000403@gmail.com>

On Wed, Sep 19, 2012 at 08:41:38PM +0200, Erwan Velu wrote:
> Hi there,
> 
> I'm using on a daily use and in production 3.2.x kernels (.29 currently) on a Kontron Nano-etx board that features the pch_gbe network driver.
> 
> I've been experiencing lots of troubles on this kernel series but since I've backported the following commits back to my 3.2.x, it works far better.
> 
> So from the history of next the following commits apply perfectly and runs very well.
> 
> I do think that other users of pch_gbe will appreciate this.
> 
> 1a0bdadb4e36abac63b0a9787f372aac30c11a9e
[...]

This first one is adding support for an extra hardware feature, which
is not suitable material for stable.  Please pick out only the
important bug fixes, per Documentation/stable_kernel_rules.txt.

If you want the driver to be completely backported, look at the
compat-drivers project
<https://backports.wiki.kernel.org/index.php/Documentation/compat-drivers>
or distribution kernels instead of stable.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus

      reply	other threads:[~2012-09-19 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 18:41 Opportunity to backport pch_gbe patches to stable 3.2.x Erwan Velu
2012-09-19 20:49 ` Ben Hutchings [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=20120919204905.GE29217@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=erwanaliasr1@gmail.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 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.