qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Dmitry Fleytman <dmitry@daynix.com>,
	Yan Vugenfirer <yan@daynix.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	P J P <ppandit@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/5] A few VLAN-related bugfixes for RX packet abstraction
Date: Sat, 4 Mar 2017 09:59:18 +0800	[thread overview]
Message-ID: <849e5f07-9e96-3f02-ace8-dd11a64e14b2@redhat.com> (raw)
In-Reply-To: <CAFEAcA_KqCnxGprcz8yTYwANVqb73Jtm8aU6gXwmDD_P6N7XGQ@mail.gmail.com>



On 2017年03月03日 20:06, Peter Maydell wrote:
> On 17 February 2017 at 03:04, Jason Wang <jasowang@redhat.com> wrote:
>>
>> On 2017年02月16日 20:29, Dmitry Fleytman wrote:
>>> This series fix a few issues related
>>> to processing of RX packets with VLAN headers.
>>>
>>> See commit messages of specific patches
>>> for information regarding affected devices.
>>>
>>> Dmitry Fleytman (5):
>>>     eth: Extend vlan stripping functions
>>>     NetRxPkt: Fix memory corruption on VLAN header stripping
>>>     NetRxPkt: Do not try to pull more data than present
>>>     NetRxPkt: Account buffer with ETH header in IOV length
>>>     NetRxPkt: Remove code duplication in net_rx_pkt_pull_data()
>>>
>>>    hw/net/net_rx_pkt.c | 40 +++++++++++++++++++++-------------------
>>>    include/net/eth.h   |  4 ++--
>>>    net/eth.c           | 25 ++++++++++++++-----------
>>>    3 files changed, 37 insertions(+), 32 deletions(-)
>>>
>> Applied. Thanks
> Hi Jason -- what's the status of these patches? I don't
> see them in master and I don't think you have them in a pull
> request yet (though I may have missed it in the deluge of
> freeze-deadline pulls...)
>
> thanks
> -- PMM
>

Already queued but haven't sent the pull request.

Plan to send it next Monday.

Thanks

      reply	other threads:[~2017-03-04  1:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 12:29 [Qemu-devel] [PATCH 0/5] A few VLAN-related bugfixes for RX packet abstraction Dmitry Fleytman
2017-02-16 12:29 ` [Qemu-devel] [PATCH 1/5] eth: Extend vlan stripping functions Dmitry Fleytman
2017-03-03 16:52   ` Philippe Mathieu-Daudé
2017-03-05  7:20     ` Dmitry Fleytman
2017-02-16 12:29 ` [Qemu-devel] [PATCH 2/5] NetRxPkt: Fix memory corruption on VLAN header stripping Dmitry Fleytman
2017-02-16 12:29 ` [Qemu-devel] [PATCH 3/5] NetRxPkt: Do not try to pull more data than present Dmitry Fleytman
2017-03-03 16:43   ` Philippe Mathieu-Daudé
2017-02-16 12:29 ` [Qemu-devel] [PATCH 4/5] NetRxPkt: Account buffer with ETH header in IOV length Dmitry Fleytman
2017-03-03 16:39   ` Philippe Mathieu-Daudé
2017-03-05  7:15     ` Dmitry Fleytman
2017-02-16 12:29 ` [Qemu-devel] [PATCH 5/5] NetRxPkt: Remove code duplication in net_rx_pkt_pull_data() Dmitry Fleytman
2017-02-19  4:02   ` Philippe Mathieu-Daudé
2017-02-16 12:39 ` [Qemu-devel] [PATCH 0/5] A few VLAN-related bugfixes for RX packet abstraction Peter Maydell
2017-02-17  3:05   ` Jason Wang
2017-02-17  4:57     ` Dmitry Fleytman
2017-02-17  3:04 ` Jason Wang
2017-03-03 12:06   ` Peter Maydell
2017-03-04  1:59     ` Jason Wang [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=849e5f07-9e96-3f02-ace8-dd11a64e14b2@redhat.com \
    --to=jasowang@redhat.com \
    --cc=dmitry@daynix.com \
    --cc=peter.maydell@linaro.org \
    --cc=ppandit@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yan@daynix.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).