From: Jeff Garzik <jgarzik@pobox.com>
To: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
Cc: akpm@linux-foundation.org, info@dcombus.com, netdev@vger.kernel.org
Subject: Re: [PATCH] wan: new driver retina
Date: Thu, 25 Oct 2007 05:18:36 -0400 [thread overview]
Message-ID: <47205F6C.7000907@pobox.com> (raw)
In-Reply-To: <586461.49400.qm@web52009.mail.re2.yahoo.com>
Not sure what's going on, but your patch looks scrambled, as scripts
look at it:
> From: Matti Linnanvuori <mattilinnanvuori@yahoo.com>=0A=0AAdding Retina G.7=
> 03 and G.SHDSL driver.=0A=0ASigned-off-by: Matti Linnanvuori <mattilinnanvu=
> ori@yahoo.com>=0A---=0A=0AFixing bugs and style according to netdev mailing=
> list comments.=0A=0Adiff -Napur linux-2.6.23/drivers/net/wan/Kconfig linux=
> -2.6.24/drivers/net/wan/Kconfig=0A--- linux-2.6.23/drivers/net/wan/Kconfig=
> =092007-10-09 23:31:38.000000000 +0300=0A+++ linux-2.6.24/drivers/net/wan/K=
> config=092007-10-25 09:23:19.933170522 +0300=0A@@ -494,4 +494,15 @@ config =
> SBNI_MULTILINE=0A =0A =09 If unsure, say N.=0A =0A+config RETINA=0A+=09tri=
> state "Retina support"=0A+=09depends on PCI=0A+=09help=0A+=09 Driver for R=
Its been mangled into "Content-Transfer-Encoding: quoted-printable" by
your mailer.
Also, when you revise a patch, please note somehow that this is an
updated version. One convention is changing the subject line:
[PATCH v3] wan: new driver retina
Otherwise I have an mbox full of seemingly-similar patches, all with the
subject "wan: new driver retina"
Jeff
next prev parent reply other threads:[~2007-10-25 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 6:49 [PATCH] wan: new driver retina Matti Linnanvuori
2007-10-25 9:18 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-23 9:58 Matti Linnanvuori
2007-10-23 16:31 ` Stephen Hemminger
2007-10-22 11:14 Matti Linnanvuori
2007-10-22 15:02 ` Randy Dunlap
2007-10-23 0:41 ` Krzysztof Halasa
2007-10-22 9:15 Matti Linnanvuori
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=47205F6C.7000907@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=info@dcombus.com \
--cc=mattilinnanvuori@yahoo.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).