All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <f.fainelli@gmail.com>, <hkallweit1@gmail.com>,
	<davem@davemloft.net>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] TI DP8382x Phy support update
Date: Fri, 10 Jan 2020 13:28:04 -0600	[thread overview]
Message-ID: <2e9333e1-1ee7-80ce-fab4-a98a9f4b345f@ti.com> (raw)
In-Reply-To: <20200110192524.GO19739@lunn.ch>

Andrew

On 1/10/20 1:25 PM, Andrew Lunn wrote:
> On Fri, Jan 10, 2020 at 12:46:58PM -0600, Dan Murphy wrote:
>> Hello
>>
>> These patches update and fix some issue found in the TI ethernet PHY drivers.
> Hi Dan
>
> Please could you separate fixes from new functionality. Have the fixes
> based on net, and new functionality on net-next.

You mean separate series between fixes and functionality?

Sure I can separate them but they are dependent on each other.

3 and 4 will not apply cleanly if patch 1 and 2 are not merged first.

Did you want patch 1 and patch 2 sent separately or together as part of 
their own series?

Dan



  reply	other threads:[~2020-01-10 19:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 18:46 [PATCH 0/4] TI DP8382x Phy support update Dan Murphy
2020-01-10 18:46 ` [PATCH 1/4] net: phy: DP83TC811: Fix typo in Kconfig Dan Murphy
2020-01-10 19:25   ` Andrew Lunn
2020-01-10 18:47 ` [PATCH 2/4] net: phy: DP83822: Update Kconfig with DP83825I support Dan Murphy
2020-01-10 19:26   ` Andrew Lunn
2020-01-10 18:47 ` [PATCH 3/4] phy: dp83826: Add phy IDs for DP83826N and 826NC Dan Murphy
2020-01-10 18:47 ` [PATCH 4/4] net: phy: DP83822: Add support for additional DP83825 devices Dan Murphy
2020-01-10 19:25 ` [PATCH 0/4] TI DP8382x Phy support update Andrew Lunn
2020-01-10 19:28   ` Dan Murphy [this message]
2020-01-10 19:40     ` Andrew Lunn
2020-01-10 19:42       ` Dan Murphy

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=2e9333e1-1ee7-80ce-fab4-a98a9f4b345f@ti.com \
    --to=dmurphy@ti.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.