From: David Miller <davem@davemloft.net>
To: martin@wetterwald.eu
Cc: andrew@lunn.ch, steve.glendinning@shawell.net,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v3] smsc95xx: Add comments to the registers definition
Date: Wed, 12 Apr 2017 10:46:05 -0400 (EDT) [thread overview]
Message-ID: <20170412.104605.1126970886368700459.davem@davemloft.net> (raw)
In-Reply-To: <20170412092405.doyczwsqnzkizarz@SMX-2>
From: Martin Wetterwald <martin@wetterwald.eu>
Date: Wed, 12 Apr 2017 11:24:05 +0200
> This chip is used by a lot of embedded devices and also by the Raspberry
> Pi 1, 2 & 3 which were created to promote the study of computer
> sciences. Students wanting to learn kernel / network device driver
> programming through those devices can only rely on the Linux kernel
> driver source to make their own.
>
> This commit adds a lot of comments to the registers definition to expand
> the register names.
>
> Cc: Steve Glendinning <steve.glendinning@shawell.net>
> Cc: Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>
> CC: David Miller <davem@davemloft.net>
> Signed-off-by: Martin Wetterwald <martin@wetterwald.eu>
> ---
> Changes in v3:
> * Restore previous name for TX_CMD_B_CSUM_ENABLE
Please fix the GPIO numbers as indicated by Woojung Huh.
next prev parent reply other threads:[~2017-04-12 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 8:45 [PATCH] smsc95xx: Add comments to the registers definition Martin Wetterwald
2017-04-10 13:52 ` Andrew Lunn
2017-04-12 2:18 ` David Miller
2017-04-12 9:24 ` [PATCH v3] " Martin Wetterwald
2017-04-12 9:32 ` Steve Glendinning
2017-04-12 11:57 ` Andrew Lunn
2017-04-12 14:25 ` Woojung.Huh
2017-04-12 16:01 ` martin
2017-04-12 22:10 ` Woojung.Huh-UWL1GkI3JZL3oGB3hsPCZA
2017-04-13 8:10 ` martin
2017-04-12 14:46 ` David Miller [this message]
2017-04-13 8:08 ` [PATCH v4] " Martin Wetterwald
2017-04-13 22:23 ` Woojung.Huh
2017-04-17 17:05 ` David Miller
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=20170412.104605.1126970886368700459.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=linux-usb@vger.kernel.org \
--cc=martin@wetterwald.eu \
--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 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).