From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Finn Thain" <fthain@linux-m68k.org>,
"Jason Wang" <jasowang@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Hervé Poussineau" <hpoussin@reactos.org>
Subject: [PATCH v4 0/5] dp8393x: fixes and improvements
Date: Sun, 11 Jul 2021 12:36:07 +0200 [thread overview]
Message-ID: <20210711103612.2661521-1-f4bug@amsat.org> (raw)
Hi Mark,
This should be the last respin.
Since v3:
- dropped worrying patches
- squashed migration patch
- added tags
Patch #3 (dp8393x: Store CAM registers as 16-bit) still
misses your S-o-b tag.
Based-on mips-next.
Mark Cave-Ayland (1):
dp8393x: don't force 32-bit register access
Philippe Mathieu-Daudé (4):
dp8393x: Replace address_space_rw(is_write=1) by address_space_write()
dp8393x: Replace 0x40 magic value by SONIC_REG16_COUNT definition
dp8393x: Store CAM registers as 16-bit
dp8393x: Rewrite dp8393x_get() / dp8393x_put()
hw/net/dp8393x.c | 206 ++++++++++++++++++++---------------------------
1 file changed, 87 insertions(+), 119 deletions(-)
--
2.31.1
next reply other threads:[~2021-07-11 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 10:36 Philippe Mathieu-Daudé [this message]
2021-07-11 10:36 ` [PATCH v4 1/5] dp8393x: Replace address_space_rw(is_write=1) by address_space_write() Philippe Mathieu-Daudé
2021-07-11 10:36 ` [PATCH v4 2/5] dp8393x: Replace 0x40 magic value by SONIC_REG16_COUNT definition Philippe Mathieu-Daudé
2021-07-11 19:50 ` Mark Cave-Ayland
2021-07-11 10:36 ` [PATCH v4 3/5] dp8393x: Store CAM registers as 16-bit Philippe Mathieu-Daudé
2021-07-11 10:36 ` [PATCH v4 4/5] dp8393x: Rewrite dp8393x_get() / dp8393x_put() Philippe Mathieu-Daudé
2021-07-11 10:36 ` [PATCH v4 5/5] dp8393x: don't force 32-bit register access Philippe Mathieu-Daudé
2021-07-11 19:58 ` [PATCH v4 0/5] dp8393x: fixes and improvements Mark Cave-Ayland
2021-07-11 20:28 ` Philippe Mathieu-Daudé
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=20210711103612.2661521-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=fthain@linux-m68k.org \
--cc=hpoussin@reactos.org \
--cc=jasowang@redhat.com \
--cc=laurent@vivier.eu \
--cc=mark.cave-ayland@ilande.co.uk \
--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).