From: Greg KH <gregkh@linuxfoundation.org>
To: Georgi Valkov <gvalkov@abv.bg>
Cc: Jakub Kicinski <kuba@kernel.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: Tue, 20 Jul 2021 14:54:57 +0200 [thread overview]
Message-ID: <YPbHoScEo8ZJyox6@kroah.com> (raw)
In-Reply-To: <C6AA954F-8382-461D-835F-E5CA03363D84@abv.bg>
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
next prev parent reply other threads:[~2021-07-20 12:55 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 [this message]
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
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=YPbHoScEo8ZJyox6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corsac@corsac.net \
--cc=davem@davemloft.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox