From: David Miller <davem@davemloft.net>
To: kaber@trash.net
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org, dmitry@butskoy.name,
greearb@candelatech.com
Subject: Re: [Bugme-new] [Bug 10443] New: VLAN: link level multicasts addresses disappears...
Date: Sat, 12 Apr 2008 23:11:09 -0700 (PDT) [thread overview]
Message-ID: <20080412.231109.177140746.davem@davemloft.net> (raw)
In-Reply-To: <4801A353.2000906@trash.net>
From: Patrick McHardy <kaber@trash.net>
Date: Sun, 13 Apr 2008 08:08:19 +0200
> Dave, could you forward them to -stable please in case you're
> fine with them? Thanks.
I've already forwarded the second one, but not the first.
I'll forward that one too, thanks!
prev parent reply other threads:[~2008-04-13 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10443-10286@http.bugzilla.kernel.org/>
2008-04-12 4:41 ` [Bugme-new] [Bug 10443] New: VLAN: link level multicasts addresses disappears Andrew Morton
2008-04-12 7:10 ` David Miller
2008-04-13 5:44 ` Patrick McHardy
2008-04-13 6:08 ` Patrick McHardy
2008-04-13 6:11 ` 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=20080412.231109.177140746.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=dmitry@butskoy.name \
--cc=greearb@candelatech.com \
--cc=kaber@trash.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).