linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Van Asbroeck <thesven73@gmail.com>
To: George McCollister <george.mccollister@gmail.com>
Cc: Bryan Whitehead <bryan.whitehead@microchip.com>,
	David S Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
	netdev <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v1] lan743x: fix ethernet frame cutoff issue
Date: Fri, 9 Apr 2021 10:38:38 -0400	[thread overview]
Message-ID: <CAGngYiV6Msz8nkM7wegk4DEL+RAeYGNk+cufuz+nTHKNqtuk5A@mail.gmail.com> (raw)
In-Reply-To: <CAFSKS=OQ0wv7mWVcZrDdrP_1WKZ+sGPZWyNMV6snc7SWRi-o5A@mail.gmail.com>

Hi George,

On Fri, Apr 9, 2021 at 10:12 AM George McCollister
<george.mccollister@gmail.com> wrote:
>
> I'm glad everyone was able to work together to get this fixed properly
> without any figure pointing or mud slinging! Kudos everyone.

Same, this is what the kernel community is supposed to be all about.

And thank you for testing+reviewing. And for not freaking out too much
when I lobbed that revert patch in your general direction :-]

  reply	other threads:[~2021-04-09 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  0:39 [PATCH net v1] lan743x: fix ethernet frame cutoff issue Sven Van Asbroeck
2021-04-09  1:02 ` Andrew Lunn
2021-04-09  1:13   ` Sven Van Asbroeck
2021-04-09 14:12 ` George McCollister
2021-04-09 14:38   ` Sven Van Asbroeck [this message]
2021-04-09 20:00 ` patchwork-bot+netdevbpf
2021-04-14 12:53 ` Julian Wiedmann
2021-04-14 13:19   ` Sven Van Asbroeck
2021-04-14 13:33     ` Julian Wiedmann
2021-04-14 13:40       ` Sven Van Asbroeck

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=CAGngYiV6Msz8nkM7wegk4DEL+RAeYGNk+cufuz+nTHKNqtuk5A@mail.gmail.com \
    --to=thesven73@gmail.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --cc=george.mccollister@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).