From: David Miller <davem@davemloft.net>
To: raghuramchary.jallipalli@microchip.com
Cc: netdev@vger.kernel.org, unglinuxdriver@microchip.com,
woojung.huh@microchip.com
Subject: Re: [PATCH v1 net 0/3] lan78xx: Fixes and enhancements
Date: Wed, 11 Apr 2018 10:20:09 -0400 (EDT) [thread overview]
Message-ID: <20180411.102009.742541645869806513.davem@davemloft.net> (raw)
In-Reply-To: <20180411072450.9809-1-raghuramchary.jallipalli@microchip.com>
From: Raghuram Chary J <raghuramchary.jallipalli@microchip.com>
Date: Wed, 11 Apr 2018 12:54:47 +0530
> These series of patches have fix and enhancements for
> lan78xx driver.
Two problems with this series:
1) Only bug fixes are appropriate at this time. Features and "enhancements"
belong in net-next which is not open right now.
2) Patch #3 doesn't even apply cleanly. Always base your patches on the
current tree.
Thank you.
next prev parent reply other threads:[~2018-04-11 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 7:24 [PATCH v1 net 0/3] lan78xx: Fixes and enhancements Raghuram Chary J
2018-04-11 7:24 ` [PATCH v1 net 1/3] lan78xx: PHY DSP registers initialization to address EEE link drop issues with long cables Raghuram Chary J
2018-04-11 7:24 ` [PATCH v1 net 2/3] lan78xx: Add support to dump lan78xx registers Raghuram Chary J
2018-04-11 18:51 ` [RFC PATCH] lan78xx: lan78xx_regs[] can be static kbuild test robot
2018-04-11 18:51 ` [PATCH v1 net 2/3] lan78xx: Add support to dump lan78xx registers kbuild test robot
2018-04-11 7:24 ` [PATCH v1 net 3/3] lan78xx: Lan7801 Support for Fixed PHY Raghuram Chary J
2018-04-11 12:55 ` [PATCH v1 net 0/3] lan78xx: Fixes and enhancements Andrew Lunn
2018-04-11 14:20 ` David Miller [this message]
2018-04-11 14:54 ` RaghuramChary.Jallipalli
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=20180411.102009.742541645869806513.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=raghuramchary.jallipalli@microchip.com \
--cc=unglinuxdriver@microchip.com \
--cc=woojung.huh@microchip.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;
as well as URLs for NNTP newsgroup(s).