From: Jason Wang <jasowang@redhat.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PULL V2 0/3] Net patches
Date: Thu, 27 May 2021 15:23:29 +0800 [thread overview]
Message-ID: <08fe1ac7-8db6-bc08-7550-b1d40eaf9039@redhat.com> (raw)
In-Reply-To: <CAEUhbmUJG9vckLWE_r=SCRpW5z1T_NZJkRy4fhUrMHAP_zbW4Q@mail.gmail.com>
在 2021/5/27 下午3:14, Bin Meng 写道:
> On Thu, May 27, 2021 at 2:35 PM Jason Wang <jasowang@redhat.com> wrote:
>>
>> 在 2021/5/27 下午2:13, Bin Meng 写道:
>>> Hi Jason,
>>>
>>> On Thu, May 27, 2021 at 12:24 PM Jason Wang <jasowang@redhat.com> wrote:
>>>> The following changes since commit d90f154867ec0ec22fd719164b88716e8fd48672:
>>>>
>>>> Merge remote-tracking branch 'remotes/dg-gitlab/tags/ppc-for-6.1-20210504' into staging (2021-05-05 20:29:14 +0100)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> https://github.com/jasowang/qemu.git tags/net-pull-request
>>>>
>>>> for you to fetch changes up to 4f8a39494aded9f2026a26b137378ea2ee3d5338:
>>>>
>>>> tap-bsd: Remove special casing for older OpenBSD releases (2021-05-27 11:03:55 +0800)
>>>>
>>>> ----------------------------------------------------------------
>>>>
>>>> ----------------------------------------------------------------
>>>> Brad Smith (1):
>>>> tap-bsd: Remove special casing for older OpenBSD releases
>>>>
>>>> Guenter Roeck (1):
>>>> hw/net/imx_fec: return 0xffff when accessing non-existing PHY
>>>>
>>>> Laurent Vivier (1):
>>>> virtio-net: failover: add missing remove_migration_state_change_notifier()
>>>>
>>>> hw/net/imx_fec.c | 8 +++-----
>>>> hw/net/trace-events | 2 ++
>>>> hw/net/virtio-net.c | 1 +
>>>> net/tap-bsd.c | 8 --------
>>>> 4 files changed, 6 insertions(+), 13 deletions(-)
>>> What happened to patch 5-12 in the following series?
>>> http://patchwork.ozlabs.org/project/qemu-devel/cover/20210317062638.72626-1-bmeng.cn@gmail.com/
>>
>> I want to do some test before the merging. Or if possible, could you
>> please write a test for this function?
>>
> For each of these network adapter models?
e1000 and virtio-net should be sufficient.
> What kind of tests are
> needed?
Test whether padding works.
> Any pointers?
You can start to look at virtio-net-test.c.
Thanks
>
> Regards,
> Bin
>
next prev parent reply other threads:[~2021-05-27 7:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 4:24 [PULL V2 0/3] Net patches Jason Wang
2021-05-27 4:24 ` [PULL V2 1/3] hw/net/imx_fec: return 0xffff when accessing non-existing PHY Jason Wang
2021-05-27 4:24 ` [PULL V2 2/3] virtio-net: failover: add missing remove_migration_state_change_notifier() Jason Wang
2021-05-27 4:24 ` [PULL V2 3/3] tap-bsd: Remove special casing for older OpenBSD releases Jason Wang
2021-05-27 6:13 ` [PULL V2 0/3] Net patches Bin Meng
2021-05-27 6:35 ` Jason Wang
2021-05-27 7:14 ` Bin Meng
2021-05-27 7:23 ` Jason Wang [this message]
2021-05-30 17:33 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-07-28 9:10 Jason Wang
2020-07-28 16:14 ` Peter Maydell
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=08fe1ac7-8db6-bc08-7550-b1d40eaf9039@redhat.com \
--to=jasowang@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).