netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Domen Puncer <domen@coderock.org>
To: Ismail Donmez <ismail@kde.org.tr>
Cc: kernel-janitors@lists.osdl.org, jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [KJ] [PATCH] Documentation/networking/dmfe.txt : Make documentation nicer
Date: Wed, 27 Apr 2005 19:07:04 +0200	[thread overview]
Message-ID: <20050427170703.GA3762@nd47.coderock.org> (raw)
In-Reply-To: <200504262244.01258.ismail@kde.org.tr>

On 26/04/05 22:44 +0300, Ismail Donmez wrote:
> Hi,
> 
> attached patch indents dmfe.txt to look like other docs. It adds a tip about 
> CNET cards using Davicom chipsets. Also it removes parts where it refers to 
> how to build driver out-of-kernel which seems to be cruft from times where 
> the driver was out of the kernel.

Please, no quoted-printable, it makes it hard for scripts to parse right.
(=20 and similar "characters")

> 
> Signed-off-by: ??smail Dönmez <ismail@kde.org.tr>

Uhh... I don't recall being discussed in which encoding this should be,
ascii is a safe bet.

> --- dmfe.txt	2004-07-24 09:45:13.000000000 +0300
> +++ dmfe2.txt	2004-07-24 09:46:37.000000000 +0300

Patch should be -p1 appliable... meaning these lines will be something like:
--- linux-2.6.12-rc3/Documentation/dmfe.txt ...
+++ linux-dev/Documentation/dmfe.txt ...

> @@ -1,59 +1,65 @@
> -  dmfe.c: Version 1.28        01/18/2000
> +Davicom DM9102(A)/DM9132/DM9801 fast ethernet driver for Linux. 

Trailing whitespace.

  reply	other threads:[~2005-04-27 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 19:44 [KJ] [PATCH] Documentation/networking/dmfe.txt : Make documentation nicer Ismail Donmez
2005-04-27 17:07 ` Domen Puncer [this message]
2005-04-27 17:26   ` Ismail Donmez
2005-04-30  8:42     ` Ismail Donmez

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=20050427170703.GA3762@nd47.coderock.org \
    --to=domen@coderock.org \
    --cc=ismail@kde.org.tr \
    --cc=jgarzik@pobox.com \
    --cc=kernel-janitors@lists.osdl.org \
    --cc=netdev@oss.sgi.com \
    /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).