public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: dragonfly@linux-vs.org
Cc: alan@lxorguk.ukuu.org.uk, marcelo.tosatti@cyclades.com,
	jiwang@ios.ac.cn, linux-kernel@vger.kernel.org
Subject: Re: kernel-2.4.32 'drivers/net' bugs acknowledgement
Date: 26 Apr 2006 07:20:41 +0200	[thread overview]
Message-ID: <p73bquo9al2.fsf@bragg.suse.de> (raw)
In-Reply-To: <1146027138.444efc82168e4@mail.linux-vs.org>

dragonfly@linux-vs.org writes:

> Hi,
>     Recently, I did a cursory check to the 'drivers/net' directory of
> the official 2.4.32 kernel sources with the help of a validity check
> tool i developed. The following are the bugs i think to be,
> sincerely apply your acknowledgement. Hope it helpful to improve great
> Linux. 

Can you perhaps do the same checks on 2.6? 2.4 is very old.

-Andi

      reply	other threads:[~2006-04-26  5:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26  4:52 kernel-2.4.32 'drivers/net' bugs acknowledgement dragonfly
2006-04-26  5:20 ` Andi Kleen [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=p73bquo9al2.fsf@bragg.suse.de \
    --to=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dragonfly@linux-vs.org \
    --cc=jiwang@ios.ac.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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