All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Smith <paul@mad-scientist.us>
To: David Miller <davem@davemloft.net>
Cc: fubar@us.ibm.com, netdev@vger.kernel.org
Subject: Re: 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying toifenslave a second interface to my bond
Date: Mon, 04 May 2009 20:59:40 -0400	[thread overview]
Message-ID: <1241485181.6499.678.camel@homebase.localnet> (raw)
In-Reply-To: <1241476694.8305.234.camel@psmith-ubeta.netezza.com>

Whew!  I was a bit worried there :-)

Can we re-queue this for 2.6.27-stable then?  I've got the patch already
building in my tree but it'd be nice to get it there by default going
forward.

Cheers!

  parent reply	other threads:[~2009-05-05  1:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 21:15 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying to ifenslave a second interface to my bond Paul Smith
2009-04-14 16:01 ` Paul Smith
2009-04-14 21:29   ` Brian Haley
2009-04-15  1:12 ` Jay Vosburgh
2009-04-15  3:23   ` David Miller
2009-04-15  5:29   ` Paul Smith
2009-04-15 16:56   ` Paul Smith
2009-04-15 18:11     ` Jay Vosburgh
2009-04-15 18:39       ` Paul Smith
     [not found] ` <1241397581.6499.658.camel@homebase.localnet>
2009-05-04 19:03   ` 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying toifenslave " Jay Vosburgh
2009-05-04 19:06     ` David Miller
2009-05-04 22:38       ` Paul Smith
2009-05-04 22:44         ` David Miller
2009-05-05  0:59         ` Paul Smith [this message]
2009-05-04 23:00       ` 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" tryingtoifenslave " Jay Vosburgh
2009-05-04 23:04         ` David Miller
2009-05-04 23:05       ` 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying toifenslave " Ben Hutchings
2009-05-04 23:12         ` David Miller
2009-05-05  4:32     ` David Miller

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=1241485181.6499.678.camel@homebase.localnet \
    --to=paul@mad-scientist.us \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@vger.kernel.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.