public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	rt2400-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Spammed logs again rt2500pci 2.6.25-rc6-00268-gd2532dd
Date: Tue, 25 Mar 2008 16:35:36 +0100	[thread overview]
Message-ID: <200803251635.36857.IvDoorn@gmail.com> (raw)
In-Reply-To: <20080325160848.6dc3584f@Varda>

On Tuesday 25 March 2008, Alejandro Riveira Fernández wrote:
> El Tue, 25 Mar 2008 14:41:22 +0100
> Ivo van Doorn <ivdoorn@gmail.com> escribió:
> 
> > Hi,
> > 
> > >  Linux Varda 2.6.25-rc6-00268-gd2532dd #1 SMP PREEMPT Mon Mar 24 14:44:13 CET
> > > 2008 x86_64 GNU/Linux
> > > 
> > > 
> > >  As the last time the thing is triggered with a p2p app making a lot of
> > >  connections deluge
> > >  
> > >  My logs are spammed with the same msgs as other reports.
> > >  If you need more info just ask.
> > 
> > This issue has been resolved for 2.6.26. The fix for this bug is of such a scale
> > that it could not easily be merged for 2.6.25.
> > 
> > >  PS: i will not bother to make a report in the web forums becouse the last time
> > > i was ignored.
> > 
> > You mean http://rt2x00.serialmonkey.com/phpBB2/index.php?
> > 'ignored' is not the right word, more likely overlooked.
> 
>  Fair enough; english is not my mother tongue so maybe i sounded
> harsher than intended. If that's the case my apologies

Ok.

> > There are quite a lot of messages and I don't always have time to answer them all.
> > So there is no need to be upset about such thing, simply posting a reminder is usually
> > enough to make it noticed by me...
> > 
> > > (Someone may want to change the web forums pointer in the logs to 
> > > the linux-wireless mailing list)
> > 
> > What pointer? And rt2400-devel is the mailinglist for rt2x00...
> > The MAINTAINERS file in the kernel tree indicates 2 mailinglists for rt2x00:
> > 	rt2400-devel@lists.sourceforge.net
> > 	linux-wireless@vger.kernel.org
> 
>  Well my opinion is that instead of the webpage the mailing list should be the
> one being logged. Something like this (maybe use another define becouse
> DRV_PROJECT may be used elsewhere i havn't checked):

Well DRV_PROJECT is the link to the website, that contains more information
about the project. When people want to report bugs they can choose to
use the bugzilla, forum or mailinglist.
So I don't see a big point in replacing the link.

Ivo

      reply	other threads:[~2008-03-25 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 21:57 Spammed logs again rt2500pci 2.6.24-rc8 Alejandro Riveira Fernández
2008-01-18 10:56 ` Mattias Nissler
2008-01-18 11:26   ` Alejandro Riveira Fernández
2008-03-25 12:12 ` Spammed logs again rt2500pci 2.6.25-rc6-00268-gd2532dd Alejandro Riveira Fernández
2008-03-25 13:41   ` Ivo van Doorn
2008-03-25 13:46     ` Ivo van Doorn
2008-03-25 15:46       ` Alejandro Riveira Fernández
2008-03-25 15:08     ` Alejandro Riveira Fernández
2008-03-25 15:35       ` Ivo van Doorn [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=200803251635.36857.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=ariveira@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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