public inbox for kernel-testers@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: a.beregalov@gmail.com
Cc: roel.kluin@gmail.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, linux-next@vger.kernel.org,
	kernel-testers@vger.kernel.org
Subject: Re: next-20090318: sunhme does not transmit packets
Date: Tue, 24 Mar 2009 13:23:55 -0700 (PDT)	[thread overview]
Message-ID: <20090324.132355.234010341.davem@davemloft.net> (raw)
In-Reply-To: <a4423d670903240850w223cdb74k7165ffd70cd7b357@mail.gmail.com>

From: Alexander Beregalov <a.beregalov@gmail.com>
Date: Tue, 24 Mar 2009 18:50:55 +0300

> 2009/3/24 Alexander Beregalov <a.beregalov@gmail.com>:
> > e4a389a9b5c892446b5de2038bdc0cca8703c615 is first bad commit
> 
> No, it is wrong, sorry.
> I will do more tests tomorrow.

I bet it is the problem we are discussing here:

	http://marc.info/?l=linux-kernel&m=123789980524715&w=2

Herbert has posted two patches to try and fix this issue,
you can try the second one to see if it solves your bug
too.

      reply	other threads:[~2009-03-24 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a4423d670903180958j4847717eh99a41534633dd314@mail.gmail.com>
     [not found] ` <20090318.234451.38898787.davem@davemloft.net>
     [not found]   ` <a4423d670903190116p157b2ebfl69d270e0576c6d9a@mail.gmail.com>
     [not found]     ` <20090322.215110.261185328.davem@davemloft.net>
     [not found]       ` <20090322.215110.261185328.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-03-24 11:32         ` next-20090318: sunhme does not transmit packets Alexander Beregalov
2009-03-24 15:46           ` Alexander Beregalov
2009-03-24 15:50             ` Alexander Beregalov
2009-03-24 20:23               ` David Miller [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=20090324.132355.234010341.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=a.beregalov@gmail.com \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=roel.kluin@gmail.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