From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: jiri@resnulli.us, netdev@vger.kernel.org, jtluka@redhat.com,
zhiguohong@tencent.com, bridge@lists.linux-foundation.org,
edumazet@google.com, laine@redhat.com, mst@redhat.com
Subject: Re: [patch net/stable v2] br: fix use of ->rx_handler_data in code executed on non-rx_handler path
Date: Fri, 06 Dec 2013 16:16:27 -0500 (EST) [thread overview]
Message-ID: <20131206.161627.917770459585726728.davem@davemloft.net> (raw)
In-Reply-To: <20131206131028.41b5b8b1@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 6 Dec 2013 13:10:28 -0800
> How come you ignored my simpler fix, that used the existing logic.
> I don't like introducing this especially into the stable; much prefer
> to go back to testing the flag as was being done before.
I thought Jiri's response to your suggestion was adequate, that's
all.
I can revert and take your version if you want me to, just make
a formal submission and get agreement from Jiri.
Thanks.
next prev parent reply other threads:[~2013-12-06 21:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 15:27 [patch net/stable v2] br: fix use of ->rx_handler_data in code executed on non-rx_handler path Jiri Pirko
2013-12-05 15:35 ` Michael S. Tsirkin
2013-12-05 15:37 ` Eric Dumazet
2013-12-05 16:55 ` Stephen Hemminger
2013-12-06 2:26 ` Gao feng
2013-12-07 1:44 ` Vlad Yasevich
2013-12-06 20:43 ` David Miller
2013-12-06 21:10 ` Stephen Hemminger
2013-12-06 21:16 ` David Miller [this message]
2013-12-07 8:51 ` Jiri Pirko
2013-12-07 17:42 ` Stephen Hemminger
2013-12-07 18:18 ` Jiri Pirko
2013-12-07 19:10 ` Vlad Yasevich
2013-12-07 20:07 ` Jiri Pirko
2013-12-09 2:07 ` Vlad Yasevich
2013-12-09 9:36 ` Jiri Pirko
2013-12-09 11:58 ` Michael S. Tsirkin
2013-12-09 12:13 ` Jiri Pirko
2013-12-09 19:31 ` Vlad Yasevich
2013-12-09 21:52 ` Jiri Pirko
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=20131206.161627.917770459585726728.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=jtluka@redhat.com \
--cc=laine@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=zhiguohong@tencent.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;
as well as URLs for NNTP newsgroup(s).