From: Jarek Poplawski <jarkao2@o2.pl>
To: David Miller <davem@davemloft.net>
Cc: shemminger@linux-foundation.org, akpm@linux-foundation.org,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
pterjan@gmail.com
Subject: Re: [PATCH][NET][BRIDGE] br_if: oops in port_carrier_check
Date: Wed, 14 Feb 2007 09:07:58 +0100 [thread overview]
Message-ID: <20070214080758.GA1972@ff.dom.local> (raw)
In-Reply-To: <20070213.123553.38710118.davem@davemloft.net>
On Tue, Feb 13, 2007 at 12:35:53PM -0800, David Miller wrote:
...
> I've applied this patch, thanks everyone.
>
> Stephen, do we want this in -stable?
I got this info it went trough -mm too:
...
> From: akpm@linux-foundation.org
> Subject: - br_if-oops-in-port_carrier_check.patch removed from -mm tree
> To: jarkao2@o2.pl, mm-commits@vger.kernel.org
...
> The patch titled
> br_if: oops in port_carrier_check
> has been removed from the -mm tree. Its filename was
> br_if-oops-in-port_carrier_check.patch
>
> This patch was dropped because it was merged into mainline or a subsystem tree
Regards,
Jarek P.
prev parent reply other threads:[~2007-02-14 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 20:52 Fw: [Bugme-new] [Bug 7962] New: oops in port_carrier_check Andrew Morton
2007-02-07 22:09 ` Stephen Hemminger
2007-02-09 7:42 ` Jarek Poplawski
2007-02-09 17:52 ` Stephen Hemminger
2007-02-09 18:50 ` Pascal Terjan
2007-02-12 6:44 ` Jarek Poplawski
2007-02-12 10:28 ` [PATCH][NET][BRIDGE] br_if: " Jarek Poplawski
2007-02-12 17:47 ` Stephen Hemminger
2007-02-13 6:26 ` Jarek Poplawski
2007-02-13 19:55 ` Stephen Hemminger
2007-02-13 20:35 ` David Miller
2007-02-14 8:07 ` Jarek Poplawski [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=20070214080758.GA1972@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pterjan@gmail.com \
--cc=shemminger@linux-foundation.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.