[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80a13e9b-e026-1238-39ed-32deb5ff17b0@siemens.com>
Date: Mon, 31 Jan 2022 10:45:23 +0100
From: Jan Kiszka <jan.kiszka@...mens.com>
To: Georgi Valkov <gvalkov@....bg>,
Greg KH <gregkh@...uxfoundation.org>
CC: Jakub Kicinski <kuba@...nel.org>, <davem@...emloft.net>,
<mhabets@...arflare.com>, <luc.vanoostenryck@...il.com>,
<snelson@...sando.io>, <mst@...hat.com>,
<linux-usb@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <corsac@...sac.net>,
<matti.vuorela@...factor.fi>, <stable@...r.kernel.org>
Subject: Re: ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
Hi Georgi,
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.
Thanks,
Jan
>> On 2021-07-20, at 3:54 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
>>
>> On Tue, Jul 20, 2021 at 03:46:11PM +0300, Georgi Valkov wrote:
>>> Yes, I read it, and before my previous e-mail that I also read the link from Jakub,
>>> which essentially provides the same information.
>>>
>>> There is only one patch 0001-ipheth-fix-EOVERFLOW-in-ipheth_rcvbulk_callback.patch
>>
>> Great, send that using 'git send-email' and all is good.
>>
>>> The command I used from the example also generated a 0000-cover-letter, so
>>> I included it as well.
>>
>> Why do you need a cover letter for 1 patch?
>>
>> thanks,
>>
>> greg k-h
>>
>
--
Siemens AG, Technology
Competence Center Embedded Linux
Powered by blists - more mailing lists