From: Jakub Kicinski <kuba@kernel.org>
To: Georgi Valkov <gvalkov@abv.bg>
Cc: 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 12:22:15 +0200 [thread overview]
Message-ID: <20210720122215.54abaf53@cakuba> (raw)
In-Reply-To: <B60B8A4B-92A0-49B3-805D-809A2433B46C@abv.bg>
On Tue, 20 Jul 2021 12:37:43 +0300, Georgi Valkov wrote:
> ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
> https://github.com/openwrt/openwrt/pull/4084
>
>
> From dd109ded2b526636fff438d33433ab64ffd21583 Mon Sep 17 00:00:00 2001
> From: Georgi Valkov <gvalkov@abv.bg>
> Date: Fri, 16 Apr 2021 20:44:36 +0300
> Subject: [PATCH] ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
This is all unnecessary, IIUC you're submitting this patch for upstream
inclusion, please rebase it on the netdev/net tree, and try git
send-email on a file generated by git format-patch. Before that please
correct the fixes tag to the common format (you'll find it in docs or
follow what others do).
next prev parent reply other threads:[~2021-07-20 10:24 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 [this message]
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
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=20210720122215.54abaf53@cakuba \
--to=kuba@kernel.org \
--cc=corsac@corsac.net \
--cc=davem@davemloft.net \
--cc=gvalkov@abv.bg \
--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.