From: Oliver Neukum <oneukum@suse.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>, netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-kernel@lists.codethink.co.uk,
steve.glendinning@shawell.net, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: SMSC95xx driver updates (round 1)
Date: Wed, 14 Nov 2018 12:58:38 +0100 [thread overview]
Message-ID: <1542196718.3385.2.camel@suse.com> (raw)
In-Reply-To: <20181114115022.9584-1-ben.dooks@codethink.co.uk>
On Mi, 2018-11-14 at 11:50 +0000, Ben Dooks wrote:
> This is a series of a few driver cleanups and some fixups of the code
> for the SMSC95XX driver. There have been a few reviews, and the issues
> have been fixed so this should be ready for merging.
>
> I will work on the tx-alignment and the other bits of usbnet changes
> and produce at least two more patch series for this later.
That looks good to me.
Regards
Oliver
next prev parent reply other threads:[~2018-11-14 11:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 11:50 SMSC95xx driver updates (round 1) Ben Dooks
2018-11-14 11:58 ` Oliver Neukum [this message]
2018-11-15 18:06 ` Woojung.Huh
2018-11-16 10:49 ` Ben Dooks
2018-11-17 4:16 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2018-11-14 11:50 [1/4] usbnet: smsc95xx: fix rx packet alignment Ben Dooks
2018-11-14 11:50 ` [PATCH 1/4] " Ben Dooks
2018-11-14 11:50 [2/4] usbnet: smsc95xx: simplify tx_fixup code Ben Dooks
2018-11-14 11:50 ` [PATCH 2/4] " Ben Dooks
2018-11-14 11:50 [3/4] usbnet: smsc95xx: fix memcpy for accessing rx-data Ben Dooks
2018-11-14 11:50 ` [PATCH 3/4] " Ben Dooks
2018-11-14 11:50 [4/4] usbnet: smsc95xx: check for csum being in last four bytes Ben Dooks
2018-11-14 11:50 ` [PATCH 4/4] " Ben Dooks
2018-11-14 15:59 [4/4] " Sergei Shtylyov
2018-11-14 15:59 ` [PATCH 4/4] " Sergei Shtylyov
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=1542196718.3385.2.camel@suse.com \
--to=oneukum@suse.com \
--cc=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.net \
/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.