Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 26 Mar 2019 11:41:30 -0700 (PDT)
Message-Id: <20190326.114130.1439471441091297640.davem@davemloft.net>
To:     Kavyasree.Kotagiri@microchip.com
Cc:     andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
        quentin.schulz@bootlin.com
Subject: Re: [PATCH 0/1] net: phy: mscc: add support for VSC8514 PHY
From:   David Miller <davem@davemloft.net>
In-Reply-To: <20190325111548.25789-1-kavyasree.kotagiri@microchip.com>
References: <20190325111548.25789-1-kavyasree.kotagiri@microchip.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


This is formatted improperly.

The "[PATCH 0/N]" posting should just provide a commit message that
explains what the patch series is doing, how it is doing it, and why
it is doing it that way.

Then you have "[PATCH 1/N]", "[PATCH 2/N]" that actually contain the
patches of the series.

Have a look at how other developers submit a patch series on this
list.

Thanks.