From: Jiri Pirko <jpirko@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
shemminger@linux-foundation.org, kaber@trash.net,
fubar@us.ibm.com, nicolas.2p.debian@gmail.com,
andy@greyhouse.net
Subject: Re: [patch net-next-2.6 0/8] mostly bonding rx path changes
Date: Sat, 5 Mar 2011 10:35:00 +0100 [thread overview]
Message-ID: <20110305093459.GH5071@psychotron.redhat.com> (raw)
In-Reply-To: <1299316329.2758.75.camel@edumazet-laptop>
Sat, Mar 05, 2011 at 10:12:09AM CET, eric.dumazet@gmail.com wrote:
>Le samedi 05 mars 2011 à 09:29 +0100, Jiri Pirko a écrit :
>> This patchset focuses mainly bonding rx path changes.
>>
>> Depends on "fcoe: correct checking for bonding"
>>
>> Jiri Pirko (8):
>> af_packet: use skb->skb_iif instead of orig_dev->ifindex
>> bonding: register slave pointer for rx_handler
>> net: get rid of multiple bond-related netdevice->priv_flags
>> bonding: wrap slave state work
>> bonding: get rid of IFF_SLAVE_INACTIVE netdev->priv_flag
>> bonding: move processing of recv handlers into handle_frame()
>> net: introduce rx_handler results and logic around that
>> net: get rid of orig_dev parameter of packet handlers
>>
>
>Jiri, I do believe your changelogs are not very helpful ...
>
>Oh wait, maybe you forgot to _include_ them ?
Well, I tried to explain that in subject. I think that most of patches
are very local so additional description would be redundant. Truth is
that I could comment "net: introduce rx_handler results and logic around
that" or perhaps "bonding: move processing of recv handlers into
handle_frame()" more.
/me thinks that he needs to learn how to write novels...
Anyway. I can repost with some more text if you like.
>
>;)
>
>
next prev parent reply other threads:[~2011-03-05 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 8:29 [patch net-next-2.6 0/8] mostly bonding rx path changes Jiri Pirko
2011-03-05 8:29 ` [patch net-next-2.6 1/8] af_packet: use skb->skb_iif instead of orig_dev->ifindex Jiri Pirko
2011-03-05 16:34 ` Changli Gao
2011-03-05 8:29 ` [patch net-next-2.6 2/8] bonding: register slave pointer for rx_handler Jiri Pirko
2011-03-05 8:29 ` [patch net-next-2.6 3/8] net: get rid of multiple bond-related netdevice->priv_flags Jiri Pirko
2011-03-05 8:29 ` [patch net-next-2.6 4/8] bonding: wrap slave state work Jiri Pirko
2011-03-05 8:29 ` [patch net-next-2.6 5/8] bonding: get rid of IFF_SLAVE_INACTIVE netdev->priv_flag Jiri Pirko
2011-03-05 8:29 ` [patch net-next-2.6 6/8] bonding: move processing of recv handlers into handle_frame() Jiri Pirko
2011-03-05 8:29 ` [patch net-next-2.6 7/8] net: introduce rx_handler results and logic around that Jiri Pirko
2011-03-05 16:45 ` Changli Gao
2011-03-05 8:29 ` [patch net-next-2.6 8/8] net: get rid of orig_dev parameter of packet handlers Jiri Pirko
2011-03-05 9:12 ` [patch net-next-2.6 0/8] mostly bonding rx path changes Eric Dumazet
2011-03-05 9:35 ` Jiri Pirko [this message]
2011-03-05 10:30 ` Jiri Pirko
-- strict thread matches above, loose matches on Subject: below --
2011-03-05 10:29 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=20110305093459.GH5071@psychotron.redhat.com \
--to=jpirko@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fubar@us.ibm.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.2p.debian@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 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).