From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"maintainer:BROADCOM BCM63XX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
Richard Cochran <richardcochran@gmail.com>,
Carlo Caione <carlo@caione.org>,
Kevin Hilman <khilman@baylibre.com>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:BROADCOM BCM63XX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Amlogic Meson SoC support"
<linux-amlogic@lists.infradead.org>
Subject: Re: [PATCH net-next v3 2/2] net: phy: remove flag PHY_HAS_INTERRUPT from driver configs
Date: Fri, 9 Nov 2018 21:13:28 +0100 [thread overview]
Message-ID: <20181109201328.GW5259@lunn.ch> (raw)
In-Reply-To: <15f15b61-1dc2-e204-0a08-f2d8f73c227d@gmail.com>
On Fri, Nov 09, 2018 at 06:17:22PM +0100, Heiner Kallweit wrote:
> Now that flag PHY_HAS_INTERRUPT has been replaced with a check for
> callbacks config_intr and ack_interrupt, we can remove setting this
> flag from all driver configs.
> Last but not least remove flag PHY_HAS_INTERRUPT completely.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Thanks for removing them all.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net-next v3 2/2] net: phy: remove flag PHY_HAS_INTERRUPT from driver configs
Date: Fri, 9 Nov 2018 21:13:28 +0100 [thread overview]
Message-ID: <20181109201328.GW5259@lunn.ch> (raw)
In-Reply-To: <15f15b61-1dc2-e204-0a08-f2d8f73c227d@gmail.com>
On Fri, Nov 09, 2018 at 06:17:22PM +0100, Heiner Kallweit wrote:
> Now that flag PHY_HAS_INTERRUPT has been replaced with a check for
> callbacks config_intr and ack_interrupt, we can remove setting this
> flag from all driver configs.
> Last but not least remove flag PHY_HAS_INTERRUPT completely.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Thanks for removing them all.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH net-next v3 2/2] net: phy: remove flag PHY_HAS_INTERRUPT from driver configs
Date: Fri, 9 Nov 2018 21:13:28 +0100 [thread overview]
Message-ID: <20181109201328.GW5259@lunn.ch> (raw)
In-Reply-To: <15f15b61-1dc2-e204-0a08-f2d8f73c227d@gmail.com>
On Fri, Nov 09, 2018 at 06:17:22PM +0100, Heiner Kallweit wrote:
> Now that flag PHY_HAS_INTERRUPT has been replaced with a check for
> callbacks config_intr and ack_interrupt, we can remove setting this
> flag from all driver configs.
> Last but not least remove flag PHY_HAS_INTERRUPT completely.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Thanks for removing them all.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2018-11-09 20:13 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 17:15 [PATCH net-next v3 0/2] net: phy: replace PHY_HAS_INTERRUPT with a check for config_intr and ack_interrupt Heiner Kallweit
2018-11-09 17:15 ` Heiner Kallweit
2018-11-09 17:15 ` Heiner Kallweit
2018-11-09 17:15 ` Heiner Kallweit
2018-11-09 17:16 ` [PATCH net-next v3 1/2] " Heiner Kallweit
2018-11-09 17:16 ` Heiner Kallweit
2018-11-09 17:16 ` Heiner Kallweit
2018-11-09 17:16 ` Heiner Kallweit
2018-11-09 20:13 ` Andrew Lunn
2018-11-09 20:13 ` Andrew Lunn
2018-11-09 20:13 ` Andrew Lunn
2018-11-09 20:13 ` Andrew Lunn
2018-11-09 20:22 ` Heiner Kallweit
2018-11-09 20:22 ` Heiner Kallweit
2018-11-09 20:22 ` Heiner Kallweit
2018-11-09 20:22 ` Heiner Kallweit
2018-11-09 20:33 ` Florian Fainelli
2018-11-09 20:33 ` Florian Fainelli
2018-11-09 20:33 ` Florian Fainelli
2018-11-09 20:33 ` Florian Fainelli
2018-11-09 20:56 ` Heiner Kallweit
2018-11-09 20:56 ` Heiner Kallweit
2018-11-09 20:56 ` Heiner Kallweit
2018-11-09 20:56 ` Heiner Kallweit
2018-11-12 20:32 ` Martin Blumenstingl
2018-11-12 20:32 ` Martin Blumenstingl
2018-11-12 20:32 ` Martin Blumenstingl
2018-11-12 20:38 ` Heiner Kallweit
2018-11-12 20:38 ` Heiner Kallweit
2018-11-12 20:38 ` Heiner Kallweit
2018-11-12 21:53 ` Martin Blumenstingl
2018-11-12 21:53 ` Martin Blumenstingl
2018-11-12 21:53 ` Martin Blumenstingl
2018-11-09 20:38 ` Andrew Lunn
2018-11-09 20:38 ` Andrew Lunn
2018-11-09 20:38 ` Andrew Lunn
2018-11-09 20:38 ` Andrew Lunn
2018-11-09 17:17 ` [PATCH net-next v3 2/2] net: phy: remove flag PHY_HAS_INTERRUPT from driver configs Heiner Kallweit
2018-11-09 17:17 ` Heiner Kallweit
2018-11-09 17:17 ` Heiner Kallweit
2018-11-09 17:17 ` Heiner Kallweit
2018-11-09 20:13 ` Andrew Lunn [this message]
2018-11-09 20:13 ` Andrew Lunn
2018-11-09 20:13 ` Andrew Lunn
2018-11-09 20:13 ` Andrew Lunn
2018-11-11 17:38 ` [PATCH net-next v3 0/2] net: phy: replace PHY_HAS_INTERRUPT with a check for config_intr and ack_interrupt David Miller
2018-11-11 17:38 ` David Miller
2018-11-11 17:38 ` David Miller
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=20181109201328.GW5259@lunn.ch \
--to=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=carlo@caione.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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 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.