From: Jarod Wilson <jarod@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: ldap.tester@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: severe regression in alx ethernet driver
Date: Tue, 24 Nov 2015 11:07:39 -0500 [thread overview]
Message-ID: <20151124160739.GG38006@redhat.com> (raw)
In-Reply-To: <20151123.111610.2054291192576855643.davem@davemloft.net>
On Mon, Nov 23, 2015 at 11:16:10AM -0500, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Mon, 23 Nov 2015 11:15:30 -0500 (EST)
>
> > From: Ldap Tester <ldap.tester@gmail.com>
> > Date: Mon, 23 Nov 2015 11:00:08 -0300
> >
> >> https://bugzilla.kernel.org/show_bug.cgi?id=70761
> >
> > Patches sitting in a bugzilla entry will simply rot.
> >
> > For upstream inclusion someone must formally submit them to the netdev
> > mailing list, with proper commit message, signoffs, etc. and then the
> > patch must be fully reviewed by the community.
> >
> > Only then will it be applied and make it upstream.
>
> And amusingly, the final comment in that bugzilla is someone asking
> the patch author to do exactly this.
They do at least have a signed-off-by in the patches attached to the bug,
so I'm working on touching up the descriptions and formatting, regression
testing them on my laptop that has an alx-driven E2200 in it (which isn't
affected by this bug), and then I can ship them up for proper review.
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2015-11-24 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 21:47 severe regression in alx ethernet driver Ldap Tester
2015-11-23 14:00 ` Ldap Tester
2015-11-23 16:15 ` David Miller
2015-11-23 16:16 ` David Miller
2015-11-24 16:07 ` Jarod Wilson [this message]
2015-11-25 22:47 ` Francois Romieu
2015-11-26 4:10 ` David Miller
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=20151124160739.GG38006@redhat.com \
--to=jarod@redhat.com \
--cc=davem@davemloft.net \
--cc=ldap.tester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).