From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: Guy Martin <gmsoft@tuxicoman.be>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"kyle@mcmartin.ca" <kyle@mcmartin.ca>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
"mikulas@artax.karlin.mff.cuni.cz"
<mikulas@artax.karlin.mff.cuni.cz>,
netdev@vger.kernel.org
Subject: Re: [E1000-devel] [PATCH] e1000: Allow the driver to be used on PA RISC C8000 workstation
Date: Mon, 27 Jun 2011 20:42:13 +0200 [thread overview]
Message-ID: <1793556.1X3EUabhs6@donald.sf-tec.de> (raw)
In-Reply-To: <2567734.3Tpd1BeV4a@donald.sf-tec.de>
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]
Rolf Eike Beer wrote:
> Am Freitag, 18. März 2011, 17:39:57 schrieb Rolf Eike Beer:
> > Am Mittwoch, 2. März 2011, 21:19:24 schrieb Jesse Brandeburg:
> > > On Mon, Feb 28, 2011 at 5:40 AM, Guy Martin <gmsoft@tuxicoman.be> wrote:
> > > > Hi Jeff,
> > > >
> > > > Any luck getting this into mainline ?
> > >
> > > Hi Guy, sorry for the delay,
> > > We haven't been able to get our contacts in HP to give us a decent
> > > response so far, we are following up with them to see whats up. We
> > > have not lost the patch and are still tracking it internally.
> > >
> > > Give us a couple more weeks if that is okay and we should be able to
> > > settle this by then.
> >
> > I wonder what exactly you are waiting for? This is a sanity check that
> > we
> > disable, so no working systems could get broken by this. And every
> > single
> > C8000 seems to be affected by this and is working fine with that patch.
> > So maybe people at HP might have a clue _why_ this is screwed, but
> > until then I don't see any point in waiting.
> >
> > So please just add my tested-by and push this upstream soon. Since this
> > is basically a hardware quirk I would like to get this into stable also
> > so we may run vanilla 2.6.38.1 or something like that on C8000.
> >
> > Tested-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
>
> For the netdev folks: it's this patch we are talking about
>
> http://www.spinics.net/lists/linux-parisc/msg03091.html
>
> I would love to see that someone finally picks this up and pushes this
> upstream, CC stable. This is absolutely annoying as it breaks every time
> anyone touches the kernel on one of this machines.
>
> Jeff, David, James: can you please make a decision of who takes this and
> then just do it?
Ping?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-06-27 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A78C6259B11833419567082E2DC0C25601D8A9CA5E@orsmsx508.amr.corp.intel.com>
[not found] ` <AANLkTinga9dW9+4TQzE+f6Tt4kAEiXaprZjv+U+-a5Mq@mail.gmail.com>
[not found] ` <1538517.jd8kKEpd3f@donald.sf-tec.de>
2011-05-06 5:58 ` [E1000-devel] [PATCH] e1000: Allow the driver to be used on PA RISC C8000 workstation Rolf Eike Beer
2011-06-27 18:42 ` Rolf Eike Beer [this message]
2011-06-27 19:33 ` Matt Turner
2011-07-03 0:33 ` [E1000-devel] " Grant Grundler
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=1793556.1X3EUabhs6@donald.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gmsoft@tuxicoman.be \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@gmail.com \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--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).