From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] hw/net/lan9118: Fix RX Status FIFO PEEK value
Date: Fri, 8 Jan 2021 19:13:32 +0100 [thread overview]
Message-ID: <c2ef0b51-09fe-97f1-cd72-632d97310b4a@amsat.org> (raw)
In-Reply-To: <20210108180401.2263-2-peter.maydell@linaro.org>
On 1/8/21 7:04 PM, Peter Maydell wrote:
> A copy-and-paste error meant that the return value for register offset 0x44
> (the RX Status FIFO PEEK register) returned a byte from a bogus offset in
> the rx status FIFO. Fix the typo.
Wow, nice catch :)
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Cc: qemu-stable@nongnu.org
> Fixes: https://bugs.launchpad.net/qemu/+bug/1904954
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> hw/net/lan9118.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/net/lan9118.c b/hw/net/lan9118.c
> index ab57c02c8e1..13d469fe24f 100644
> --- a/hw/net/lan9118.c
> +++ b/hw/net/lan9118.c
> @@ -1206,7 +1206,7 @@ static uint64_t lan9118_readl(void *opaque, hwaddr offset,
> case 0x40:
> return rx_status_fifo_pop(s);
> case 0x44:
> - return s->rx_status_fifo[s->tx_status_fifo_head];
> + return s->rx_status_fifo[s->rx_status_fifo_head];
> case 0x48:
> return tx_status_fifo_pop(s);
> case 0x4c:
>
next prev parent reply other threads:[~2021-01-08 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 18:03 [PATCH 0/2] lan9118: Fix RX Status FIFO PEEK value Peter Maydell
2021-01-08 18:04 ` [PATCH 1/2] hw/net/lan9118: " Peter Maydell
2021-01-08 18:13 ` Philippe Mathieu-Daudé [this message]
2021-01-08 18:04 ` [PATCH 2/2] hw/net/lan9118: Add symbolic constants for register offsets Peter Maydell
2021-01-08 18:16 ` 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=c2ef0b51-09fe-97f1-cd72-632d97310b4a@amsat.org \
--to=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).