All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] DMA issues with ar9280 cards
Date: Wed, 23 Feb 2011 10:02:00 -0800	[thread overview]
Message-ID: <20110223180200.GF19293@tux> (raw)
In-Reply-To: <20110223162230.23968.qmail@stuge.se>

On Wed, Feb 23, 2011 at 08:22:30AM -0800, Peter Stuge wrote:
> Bernhard Schmidt wrote:
> > Felix already told me that this is a known issue and going over other
> > reports on this list and linux-wireless-ml it indeed is. Just wanted
> > to know if there is any "known-good" kernel version or a workaround
> > for that?
> 
> I fear you will not get any further info on this mailing list. I would
> suggest to watch the l-w list and try any patches that are sent there.
> 
> They never appear here and there's also no discussion here. Thinking
> about it I actually don't really understand the purpose of this list.
> It's mostly disinforming, in that it detracts from l-w, which seems
> to be the more significant forum for ath9k development.

Would you stop trolling, really. I told you what you can do to help
with resolving observed issues, where are your bug reports BTW? Trust
me that people are reading these lists, and issues do get fixed, for
some reason however *you* are not getting your issues resolved. Have
you ever stopped to really consider perhaps its not *us* and that you
can likely consider some changes on your behalf to work better with
our teams who *are* engaged in fixing issues. Your focus is to say
you are very well experienced but don't want to hack.. fine but,
given your experience you should be able to work even further with
devlopers, but that's not happening, why? Because *you* are expecting
people to simply read every e-mail rant from you digged into other
people's replies.

Make this simple, split all of your issues, document them into
bug reports for a specific kernel release, help see if you can identify
them as regressions, etc.

Have you done all this?

  LUis

  reply	other threads:[~2011-02-23 18:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 15:34 [ath9k-devel] DMA issues with ar9280 cards Bernhard Schmidt
2011-02-23 16:22 ` Peter Stuge
2011-02-23 18:02   ` Luis R. Rodriguez [this message]
2011-02-23 19:51     ` Peter Stuge
     [not found] <201102230955.35674.bschmidt@techwires.net>
2011-02-23 17:46 ` Luis R. Rodriguez
2011-02-23 18:12   ` Adrian Chadd
2011-02-23 18:20     ` Adrian Chadd
2011-02-23 18:24       ` Jouni Malinen
2011-02-23 18:40         ` Adrian Chadd
2011-02-23 23:06           ` Jouni Malinen
2011-02-23 20:06   ` Bernhard Schmidt
2011-02-24  9:33     ` Bernhard Schmidt
2011-02-24 18:18       ` Luis R. Rodriguez
2011-02-25  9:37         ` Bernhard Schmidt
2011-02-25 17:12           ` Luis R. Rodriguez
2011-02-26  9:37             ` Bernhard Schmidt
2011-03-10  0:40               ` Felix Fietkau
2011-03-02 14:51     ` Mohammed Shafi
2011-03-04 11:29       ` Bernhard Schmidt
2011-03-04 15:25         ` Mohammed Shafi
2011-03-04 15:29           ` Mohammed Shafi
2011-03-04 17:16             ` Bernhard Schmidt
2011-03-09  9:58               ` Mohammed Shafi
2011-03-09 10:01               ` Mohammed Shafi
2011-03-05 23:49         ` crocket
2011-03-09 10:22           ` Peter Stuge

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=20110223180200.GF19293@tux \
    --to=lrodriguez@atheros.com \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.