All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yves-Alexis Perez <corsac@corsac.net>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Georgi Valkov <gvalkov@abv.bg>
Cc: linux-usb <linux-usb@vger.kernel.org>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"stable @ vger . kernel . org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2 0/1] ipheth URB overflow fix
Date: Wed, 02 Feb 2022 09:09:30 +0100	[thread overview]
Message-ID: <0414e435e29d4ddf53d189d86fae2c55ed0f81ac.camel@corsac.net> (raw)
In-Reply-To: <cover.1643699778.git.jan.kiszka@siemens.com>

On Tue, 2022-02-01 at 08:16 +0100, Jan Kiszka wrote:
> Georgi Valkov (1):
>   ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
> 
>  drivers/net/usb/ipheth.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Hi,

sorry for the extra-long delay. I finally tested the patch, and it seems to
work fine. I've tried it on my laptop for few hours without issue, but to be
fair it was working just fine before, I never experienced the EOVERFLOW
myself.

Regards,
-- 
Yves-Alexis

  parent reply	other threads:[~2022-02-02  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  7:16 [PATCH v2 0/1] ipheth URB overflow fix Jan Kiszka
2022-02-01  7:16 ` [PATCH v2 1/1] ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback Jan Kiszka
2022-02-02  4:30 ` [PATCH v2 0/1] ipheth URB overflow fix patchwork-bot+netdevbpf
2022-02-02  8:09 ` Yves-Alexis Perez [this message]
2022-02-02 10:35   ` Georgi Valkov
2022-02-02 17:01     ` Yves-Alexis Perez

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=0414e435e29d4ddf53d189d86fae2c55ed0f81ac.camel@corsac.net \
    --to=corsac@corsac.net \
    --cc=davem@davemloft.net \
    --cc=gvalkov@abv.bg \
    --cc=jan.kiszka@siemens.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.