From: David Miller <davem@davemloft.net>
To: thesven73@gmail.com
Cc: Bryan.Whitehead@microchip.com, kuba@kernel.org,
UNGLinuxDriver@microchip.com, andrew@lunn.ch, rtgbnm@gmail.com,
sbauer@blackbox.su, tharvey@gateworks.com,
anders@ronningen.priv.no, hdanton@sina.com, hch@lst.de,
willemdebruijn.kernel@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/5] lan743x speed boost
Date: Wed, 17 Feb 2021 14:16:07 -0800 (PST) [thread overview]
Message-ID: <20210217.141607.975797701534267256.davem@davemloft.net> (raw)
In-Reply-To: <CAGngYiUV_c7Z-gUCt0xKcP-E_5UVyM9PWBQ_wYK9o5_L0D-1qA@mail.gmail.com>
From: Sven Van Asbroeck <thesven73@gmail.com>
Date: Wed, 17 Feb 2021 17:04:05 -0500
> Hi Jakub and Bryan,
>
> Jakub, is there anything else you'd like to see from us, before you
> are satisfied that patches 1/5 and 2/5 can be merged into your tree?
They are already merged into net-next
prev parent reply other threads:[~2021-02-17 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 1:08 Sven Van Asbroeck
2021-02-16 1:08 ` [PATCH net-next v3 1/5] lan743x: boost performance on cpu archs w/o dma cache snooping Sven Van Asbroeck
2021-02-16 1:08 ` [PATCH net-next v3 2/5] lan743x: sync only the received area of an rx ring buffer Sven Van Asbroeck
2021-02-16 20:03 ` Bryan.Whitehead
2021-02-16 21:28 ` Sven Van Asbroeck
2021-02-16 1:08 ` [PATCH net-next v3 3/5] TEST ONLY: lan743x: limit rx ring buffer size to 500 bytes Sven Van Asbroeck
2021-02-16 1:08 ` [PATCH net-next v3 4/5] TEST ONLY: lan743x: skb_alloc failure test Sven Van Asbroeck
2021-02-16 1:08 ` [PATCH net-next v3 5/5] TEST ONLY: lan743x: skb_trim " Sven Van Asbroeck
2021-02-17 21:43 ` [PATCH net-next v3 0/5] lan743x speed boost Bryan.Whitehead
2021-02-17 22:04 ` Sven Van Asbroeck
2021-02-17 22:16 ` David Miller [this message]
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=20210217.141607.975797701534267256.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Bryan.Whitehead@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=anders@ronningen.priv.no \
--cc=andrew@lunn.ch \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rtgbnm@gmail.com \
--cc=sbauer@blackbox.su \
--cc=tharvey@gateworks.com \
--cc=thesven73@gmail.com \
--cc=willemdebruijn.kernel@gmail.com \
/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
all inboxes | Powered by JetHome®