From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
syzbot <syzkaller@googlegroups.com>,
Jarod Wilson <jarod@redhat.com>, Moshe Tal <moshet@nvidia.com>,
Jussi Maki <joamaki@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net] bonding: do not assume skb mac_header is set
Date: Thu, 22 Jun 2023 12:31:39 -0700 [thread overview]
Message-ID: <27955.1687462299@famine> (raw)
In-Reply-To: <CANn89iL3kLondF3ETBui8ik3sJW+1NR8SZFYWqw7FY4H5gcUjw@mail.gmail.com>
Eric Dumazet <edumazet@google.com> wrote:
>On Thu, Jun 22, 2023 at 9:00 PM Eric Dumazet <edumazet@google.com> wrote:
>>
>
>> Ah right, I will send another patch to remove it then.
>>
>> I think it makes sense to keep the first patch small for backports.
>>
>> History of relevant patches :
>>
>> from 5.17
>>
>> 429e3d123d9a50cc9882402e40e0ac912d88cfcf bonding: Fix extraction of
>> ports from the packet headers
>>
>> from 5.15
>>
>> a815bde56b15ce626caaacc952ab12501671e45d net, bonding: Refactor
>> bond_xmit_hash for use with xdp_buff
>
>If this is ok for you, I will cook this cleanup patch for net-next.
Yes, this sounds fine to me.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2023-06-22 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 15:23 [PATCH net] bonding: do not assume skb mac_header is set Eric Dumazet
2023-06-22 17:48 ` Jay Vosburgh
2023-06-22 18:32 ` Eric Dumazet
2023-06-22 18:55 ` Jay Vosburgh
2023-06-22 19:00 ` Eric Dumazet
2023-06-22 19:01 ` Eric Dumazet
2023-06-22 19:31 ` Jay Vosburgh [this message]
2023-06-23 11:07 ` Jiri Pirko
2023-06-23 14:28 ` Eric Dumazet
2023-06-23 15:04 ` Jiri Pirko
2023-06-24 2:10 ` patchwork-bot+netdevbpf
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=27955.1687462299@famine \
--to=jay.vosburgh@canonical.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jarod@redhat.com \
--cc=joamaki@gmail.com \
--cc=kuba@kernel.org \
--cc=moshet@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller@googlegroups.com \
--cc=vladimir.oltean@nxp.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 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.