From: Murali Karicheri <m-karicheri2@ti.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v1] net: netcp: remove call to netif_carrier_(on/off) for MAC to Phy interface
Date: Mon, 27 Apr 2015 14:09:40 -0400 [thread overview]
Message-ID: <553E7B64.3080407@ti.com> (raw)
In-Reply-To: <20150427.132318.64451627276298303.davem@davemloft.net>
On 04/27/2015 01:23 PM, David Miller wrote:
> From: Murali Karicheri<m-karicheri2@ti.com>
> Date: Mon, 27 Apr 2015 13:07:35 -0400
>
>> On 04/25/2015 03:48 PM, David Miller wrote:
>>> From: Murali Karicheri<m-karicheri2@ti.com>
>>> Date: Fri, 24 Apr 2015 15:01:41 -0400
>>>
>>>> Currently when interface type is MAC to Phy, netif_carrier_(on/off)
>>>> is called which is not needed as Phy lib already updates the carrier
>>>> status to net stack. This is needed only for other interface types
>>>>
>>>> Signed-off-by: Murali Karicheri<m-karicheri2@ti.com>
>>>
>>> net-next is not open for submissions yet
>> David,
>>
>> Do I need to re-submit this patch when the net-next gets opened for
>> this? This is essentially a bug fix and can be applied to current
>
> If it's really a bug fix, then you shouldn't target it at net-next.
>
> I'll never understand why people do things like this.
Ok. My bad. I will re-send it with proper prefix for applying to v4.1.
--
Murali Karicheri
Linux Kernel, Texas Instruments
prev parent reply other threads:[~2015-04-27 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 19:01 [PATCH net-next v1] net: netcp: remove call to netif_carrier_(on/off) for MAC to Phy interface Murali Karicheri
2015-04-25 19:48 ` David Miller
2015-04-27 17:07 ` Murali Karicheri
2015-04-27 17:23 ` David Miller
2015-04-27 18:09 ` Murali Karicheri [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=553E7B64.3080407@ti.com \
--to=m-karicheri2@ti.com \
--cc=davem@davemloft.net \
--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.