From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Georgi Valkov <gvalkov@abv.bg>,
Greg KH <gregkh@linuxfoundation.org>, <davem@davemloft.net>,
<mhabets@solarflare.com>, <luc.vanoostenryck@gmail.com>,
<snelson@pensando.io>, <mst@redhat.com>,
<linux-usb@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <corsac@corsac.net>,
<matti.vuorela@bitfactor.fi>, <stable@vger.kernel.org>
Subject: Re: ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
Date: Mon, 31 Jan 2022 18:35:44 +0100 [thread overview]
Message-ID: <6108f260-36bf-0059-ccb9-8189f4a2d0c1@siemens.com> (raw)
In-Reply-To: <20220131092726.3864b19f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 31.01.22 18:27, Jakub Kicinski wrote:
> On Mon, 31 Jan 2022 10:45:23 +0100 Jan Kiszka wrote:
>> On 20.07.21 15:12, Georgi Valkov wrote:
>>> Thank you, Greg!
>>>
>>> git send-email drivers/net/0001-ipheth-fix-EOVERFLOW-in-ipheth_rcvbulk_callback.patch
>>> ...
>>> Result: OK
>>>
>>> I hope I got right. I added most of the e-mail addresses, and also tried adding Message-Id.
>>> I have not received the e-mail yet, so I cannot confirm if it worked or not.
>>>
>>
>> What happened here afterwards?
>>
>> I just found out the hard way that this patch is still not in mainline
>> but really needed.
>
> I have not seen the repost :(
Would it help if I do that on behalf of Georgi? Meanwhile, I can add a
tested-by to it, after almost a full working day with it applied.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-01-31 17:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 9:37 ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback Georgi Valkov
2021-07-20 9:58 ` Greg KH
2021-07-20 10:22 ` Jakub Kicinski
2021-07-20 11:39 ` Georgi Valkov
2021-07-20 11:49 ` Greg KH
2021-07-20 12:46 ` Georgi Valkov
2021-07-20 12:54 ` Greg KH
2021-07-20 13:12 ` Georgi Valkov
2022-01-31 9:45 ` Jan Kiszka
2022-01-31 17:27 ` Jakub Kicinski
2022-01-31 17:35 ` Jan Kiszka [this message]
2022-01-31 17:47 ` Jakub Kicinski
2022-01-31 18:46 ` Jan Kiszka
2022-01-31 21:43 ` Georgi Valkov
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=6108f260-36bf-0059-ccb9-8189f4a2d0c1@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=corsac@corsac.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=gvalkov@abv.bg \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=matti.vuorela@bitfactor.fi \
--cc=mhabets@solarflare.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=snelson@pensando.io \
--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.