devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Badel, Laurent" <LaurentBadel@eaton.com>
To: Florian Fainelli <f.fainelli@gmail.com>, Rob Herring <robh@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"fugang.duan@nxp.com" <fugang.duan@nxp.com>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"m.felsch@pengutronix.de" <m.felsch@pengutronix.de>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"richard.leitner@skidata.com" <richard.leitner@skidata.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Quette, Arnaud" <ArnaudQuette@Eaton.com>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	Heiner Kallweit <hkallweit1@gmail.com>
Subject: RE: [EXTERNAL] Re: [PATCH net 2/4] net:phy:smsc: expand documentation of clocks property
Date: Mon, 9 Nov 2020 15:16:53 +0000	[thread overview]
Message-ID: <CY4PR1701MB1878442106B8B2A3F80924E5DFEA0@CY4PR1701MB1878.namprd17.prod.outlook.com> (raw)
In-Reply-To: <da87e8d5-01f9-50c2-5583-3876f9c12c8f@gmail.com>



> 

-----------------------------
Eaton Industries Manufacturing GmbH ~ Registered place of business: Route de la Longeraie 7, 1110, Morges, Switzerland 

-----------------------------

-----Original Message-----
> From: Florian Fainelli <f.fainelli@gmail.com>
> Sent: Wednesday, November 04, 2020 5:02 PM
> To: Badel, Laurent <LaurentBadel@eaton.com>; Rob Herring
> <robh@kernel.org>
> Cc: davem@davemloft.net; fugang.duan@nxp.com; andrew@lunn.ch;
> lgirdwood@gmail.com; m.felsch@pengutronix.de; robh+dt@kernel.org;
> kuba@kernel.org; linux@armlinux.org.uk; richard.leitner@skidata.com;
> netdev@vger.kernel.org; Quette, Arnaud <ArnaudQuette@Eaton.com>;
> p.zabel@pengutronix.de; devicetree@vger.kernel.org; broonie@kernel.org;
> Heiner Kallweit <hkallweit1@gmail.com>
> Subject: Re: [EXTERNAL] Re: [PATCH net 2/4] net:phy:smsc: expand
> documentation of clocks property
> 
> 
> 
> On 11/4/2020 4:11 AM, Badel, Laurent wrote:
> > >
> >
> > -----------------------------
> > Eaton Industries Manufacturing GmbH ~ Registered place of business:
> > Route de la Longeraie 7, 1110, Morges, Switzerland
> >
> > -----------------------------
> >
> > -----Original Message-----
> >> From: Rob Herring <robh@kernel.org>
> >> Sent: Friday, October 30, 2020 8:19 PM
> >> To: Badel, Laurent <LaurentBadel@eaton.com>
> >> Cc: davem@davemloft.net; fugang.duan@nxp.com; andrew@lunn.ch;
> >> lgirdwood@gmail.com; m.felsch@pengutronix.de; robh+dt@kernel.org;
> >> kuba@kernel.org; linux@armlinux.org.uk; richard.leitner@skidata.com;
> >> netdev@vger.kernel.org; Quette, Arnaud <ArnaudQuette@Eaton.com>;
> >> p.zabel@pengutronix.de; devicetree@vger.kernel.org;
> >> f.fainelli@gmail.com; broonie@kernel.org; Heiner Kallweit
> >> <hkallweit1@gmail.com>
> >> Subject: [EXTERNAL] Re: [PATCH net 2/4] net:phy:smsc: expand
> >> documentation of clocks property
> >>
> >> On Tue, 27 Oct 2020 23:27:42 +0000, Badel, Laurent wrote:
> >>> Subject: [PATCH net 2/4] net:phy:smsc: expand documentation of
> >>> clocks property
> >>>
> >>> Description: The ref clock is managed differently when added to the
> >>> DT entry for SMSC PHY. Thus, specify this more clearly in the
> documentation.
> >>>
> >>> Signed-off-by: Laurent Badel <laurentbadel@eaton.com>
> >>> ---
> >>>  Documentation/devicetree/bindings/net/smsc-lan87xx.txt | 3 ++-
> >>>  1 file changed, 2 insertions(+), 1 deletion(-)
> >>>
> >>
> >> Acked-by: Rob Herring <robh@kernel.org>
> >
> > Thank you very much.
> > I'm guessing perhaps I should re-send this as a single patch since
> > there are issues with the patch series?
> > I realize now that I should have splitted things differently.
> 
> There are several things with your patch series that make it very hard to be
> followed or to even know what is the latest version of your patch series. If
> you can resubmit everything targeting the 'net' tree along with a cover letter
> explaining the differences between v1 and v2 that would help. Please make
> sure that all of your patches reference the cover letter's Message-Id which is
> the default if you use git format-patch --cover-letter .
> 
> Thanks
> --
> Florian

I will make sure to give details as you suggested, sorry for the trouble and thank
you for your time reviewing. 
Laurent

      reply	other threads:[~2020-11-09 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 23:27 [PATCH net 2/4] net:phy:smsc: expand documentation of clocks property Badel, Laurent
2020-10-30 19:19 ` Rob Herring
2020-11-04 12:11   ` [EXTERNAL] " Badel, Laurent
2020-11-04 16:01     ` Florian Fainelli
2020-11-09 15:16       ` Badel, Laurent [this message]

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=CY4PR1701MB1878442106B8B2A3F80924E5DFEA0@CY4PR1701MB1878.namprd17.prod.outlook.com \
    --to=laurentbadel@eaton.com \
    --cc=ArnaudQuette@Eaton.com \
    --cc=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=fugang.duan@nxp.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux@armlinux.org.uk \
    --cc=m.felsch@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=richard.leitner@skidata.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    /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).