netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "Andreas Färber" <afaerber@suse.de>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Uwe Kleine-König" <uwe@kleine-koenig.org>,
	"Michal Hrusecki" <Michal.Hrusecky@nic.cz>,
	"Tomas Hlavacek" <tomas.hlavacek@nic.cz>,
	"Bed??icha Ko??atu" <bedrich.kosata@nic.cz>,
	"Vivien Didelot" <vivien.didelot@savoirfairelinux.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] net: dsa: mv88e6xxx: Add 88E6176 device tree support
Date: Mon, 28 Nov 2016 00:10:09 +0100	[thread overview]
Message-ID: <20161127231009.GA17704@lunn.ch> (raw)
In-Reply-To: <e5d45b55-a4c1-3b5e-0bdc-a5e340b072d0@suse.de>

> Try to see it from my perspective: I see that some vf610 device I don't
> have (found via `git grep marvell,mv88e6` or so) uses
> "marvell,mv88e6085". I then assume it has that device on board. How
> would I know it doesn't? Same for the other boards you mention.
> 
> Unfortunately some of your replies are slightly cryptic. Had you simply
> replied 'please just use "marvell,mv88e6085" instead', it would've been
> much more clear what you want. (Same for extending the subject instead
> of just pointing to some FAQ.)

By reading the FAQ you have learnt more than me saying put the correct
tree in the subject line. By asking you to explain why you need a
compatible string, i'm trying to make you think, look at the code and
understand it. In the future, you might think and understand the code
before posting a patch, and then we all save time.

> So are you okay with patch 1/2 documenting the compatible? Then we could
> drop 2/2 and use "marvell,mv88e6176", "marvell,mv88e6085" instead of
> just the latter. Or would you rather drop both and keep the actual chip
> a comment?

A comment only please.

Thanks
	Andrew

  reply	other threads:[~2016-11-27 23:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 20:57 [PATCH 1/2] Documentation: net: dsa: marvell: Add 88E6176 Andreas Färber
2016-11-27 20:57 ` [PATCH 2/2] net: dsa: mv88e6xxx: Add 88E6176 device tree support Andreas Färber
2016-11-27 21:27   ` Andrew Lunn
2016-11-27 21:50     ` Andreas Färber
2016-11-27 22:08       ` Andrew Lunn
2016-11-27 22:42         ` Andreas Färber
2016-11-27 23:10           ` Andrew Lunn [this message]
2016-11-28  8:09             ` Uwe Kleine-König
     [not found]               ` <20161128080939.ippqlytvojitefkp-jgopVnDzZD+b0XQX99//ntPVjbGH4+40kFgPdswSElo@public.gmane.org>
2016-11-28 13:17                 ` Andrew Lunn
     [not found]                   ` <20161128131735.GA4379-g2DYL2Zd6BY@public.gmane.org>
2016-11-28 15:44                     ` Uwe Kleine-König
     [not found]                       ` <2c59cc79-b6dc-9920-1725-a7785ff3b6bf-rXY34ruvC2xidJT2blvkqNi2O/JbrIOy@public.gmane.org>
2016-11-28 16:14                         ` Andrew Lunn
2016-11-29 17:54                       ` Vivien Didelot
     [not found]                         ` <87oa0yb29b.fsf-BOtmAI95c/+pXNIQCVAXCG0Lkn3mC4nZ0tOlhedn3YvkypF1WZHjJXhe7Zk3YmMvjmZSf7Nhrd8@public.gmane.org>
2016-11-29 18:20                           ` Andrew Lunn

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=20161127231009.GA17704@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Michal.Hrusecky@nic.cz \
    --cc=afaerber@suse.de \
    --cc=bedrich.kosata@nic.cz \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tomas.hlavacek@nic.cz \
    --cc=uwe@kleine-koenig.org \
    --cc=vivien.didelot@savoirfairelinux.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).