public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Sven Van Asbroeck <svendev@arcx.com>,
	Woojung.Huh@microchip.com, Tristram.Ha@microchip.com
Cc: f.fainelli@gmail.com, helmut.buchsbaum@gmail.com,
	Maarten.Blomme@flir.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH v1 0/1] spi_ks8995: use regmap to access chip registers.
Date: Tue, 6 Feb 2018 17:14:47 +0100	[thread overview]
Message-ID: <20180206161447.GF12679@lunn.ch> (raw)
In-Reply-To: <1517930036-17618-1-git-send-email-svendev@arcx.com>

On Tue, Feb 06, 2018 at 10:13:55AM -0500, Sven Van Asbroeck wrote:
> v1:
> 	starting point.
> 	is there a way to test-run this on supported devices that I don't
> 		have physical access to - (ks8995, ksz8864) ?
> 
> Sven Van Asbroeck (1):
>   spi_ks8995: use regmap to access chip registers.

Hi Sven

Rather than invest time in this driver, it would be better to look
into writing a DSA driver. There was some effort last year to make the
current microchip DSA driver more generic, but that has gone quiet
recently. Maybe you can talk to Tristram.Ha@microchip.com and
Woojung.Huh@microchip.com

	Andrew

  parent reply	other threads:[~2018-02-06 16:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 15:13 [PATCH v1 0/1] spi_ks8995: use regmap to access chip registers Sven Van Asbroeck
2018-02-06 15:13 ` [PATCH v1 1/1] " Sven Van Asbroeck
2018-02-08  2:49   ` David Miller
2018-02-06 16:14 ` Andrew Lunn [this message]
2018-02-06 16:41   ` [PATCH v1 0/1] " Sven Van Asbroeck
2018-02-06 16:50     ` Andrew Lunn
2018-02-06 16:58       ` Sven Van Asbroeck
2018-02-06 17:05         ` Andrew Lunn
2018-02-06 17:47           ` Florian Fainelli
2018-02-06 18:11             ` 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=20180206161447.GF12679@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Maarten.Blomme@flir.com \
    --cc=Tristram.Ha@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=f.fainelli@gmail.com \
    --cc=helmut.buchsbaum@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=svendev@arcx.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