qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: "Tomasz Dzieciol/VIM Integration (NC) /SRPOL/Engineer/Samsung
	Electronics" <t.dzieciol@partner.samsung.com>,
	qemu-devel@nongnu.org
Cc: sriram.yagnaraman@est.tech, jasowang@redhat.com,
	k.kwiecien@samsung.com, m.sochacki@samsung.com
Subject: Re: [PATCH v3 1/2] igb: RX descriptors handling cleanup
Date: Sun, 30 Apr 2023 15:05:50 +0900	[thread overview]
Message-ID: <a904ce6c-08e5-e4ed-6250-00940ad73fd4@daynix.com> (raw)
In-Reply-To: <000001d979d0$23571b90$6a0552b0$@partner.samsung.com>

On 2023/04/28 21:51, Tomasz Dzieciol/VIM Integration (NC) 
/SRPOL/Engineer/Samsung Electronics wrote:
>> Please don't ignore comments in reviews, and if you have a question with them or you don't agree with them, please write so in a reply. You don't have to post a new version quickly so take time to address all problems pointed out.
> 
> I assumed that comments referred only to places pointed in the code and fixed only those places. Sorry about that. I will keep in mind that your comments are more general and fix all the places, where array is passed as parameter.
> 
>> Please split up those changes into separate patches.
> 
> I will extract TCP ACK detection removal and IPv6 extensions traffic detection to separate patches. Those will be small patches in comparison to the rest of cleanup, however those are functional changes.
> 
>> Do *not*:
>> - suffix struct name with _st. The convention is not common in QEMU code base, or even e1000e and igb do not always use the suffixes.
>> - use _.
> 
> ok, I was looking at E1000E_RingInfo_st, which was added recently with IGB code in commit 3a977deebe6b9a10043182e922f6883924ef21f5 ("Intrdocue igb device emulation").

It's just copied from e1000e code. Check for e1000e_core.c for history 
older than that commit.


  reply	other threads:[~2023-04-30  6:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230427104749eucas1p19480869211eed34117a518f3c3800946@eucas1p1.samsung.com>
2023-04-27 10:47 ` [PATCH v3 0/2] igb: packet-split descriptors support Tomasz Dzieciol
     [not found]   ` <CGME20230427104750eucas1p1158eee5a37c71cacaea021a7abbd6ace@eucas1p1.samsung.com>
2023-04-27 10:47     ` [PATCH v3 1/2] igb: RX descriptors handling cleanup Tomasz Dzieciol
2023-04-28 10:31       ` Akihiko Odaki
2023-04-28 12:51         ` Tomasz Dzieciol/VIM Integration (NC) /SRPOL/Engineer/Samsung Electronics
2023-04-30  6:05           ` Akihiko Odaki [this message]
2023-04-28 12:53         ` Tomasz Dzieciol/VIM Integration (NC) /SRPOL/Engineer/Samsung Electronics
2023-04-30 11:57       ` Sriram Yagnaraman
2023-05-02 14:00         ` Tomasz Dzieciol/VIM Integration (NC) /SRPOL/Engineer/Samsung Electronics
2023-05-03  7:46           ` Sriram Yagnaraman
2023-05-03 15:11             ` Akihiko Odaki
2023-05-04  7:37               ` Tomasz Dzieciol/VIM Integration (NC) /SRPOL/Engineer/Samsung Electronics
     [not found]   ` <CGME20230427104750eucas1p1eb8fb7fac00cc13dea5e4a7e0df5c113@eucas1p1.samsung.com>
2023-04-27 10:47     ` [PATCH v3 2/2] igb: packet-split descriptors support Tomasz Dzieciol

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=a904ce6c-08e5-e4ed-6250-00940ad73fd4@daynix.com \
    --to=akihiko.odaki@daynix.com \
    --cc=jasowang@redhat.com \
    --cc=k.kwiecien@samsung.com \
    --cc=m.sochacki@samsung.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sriram.yagnaraman@est.tech \
    --cc=t.dzieciol@partner.samsung.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).