From: Andrew Lunn <andrew@lunn.ch>
To: "Modi, Geet" <geet.modi@ti.com>
Cc: "Nagalla, Hari" <hnagalla@ti.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Sharma, Vikram" <vikram.sharma@ti.com>,
dmurphy@ti.com
Subject: Re: [EXTERNAL] Re: [EXTERNAL] Re: [EXTERNAL] Re: [PATCH] net: phy: dp83tc811: modify list of interrupts enabled at initialization
Date: Fri, 10 Sep 2021 03:30:48 +0200 [thread overview]
Message-ID: <YTq1SATpNvwo+ojg@lunn.ch> (raw)
In-Reply-To: <E3DBDC45-111F-4744-82A8-95C7D5CCEBE5@ti.com>
On Fri, Sep 10, 2021 at 12:41:53AM +0000, Modi, Geet wrote:
> Hi Andrew,
>
> As mentioned we want to do this in phases:
> a) this patch to disable the Overvoltage driver interrupt
> b) After carefully considering other interrupts, plan a follow-on patch to take care of other interrupts.
I still don't get it. Why just Over volt now and not the rest, which
are equally useless? It makes me think there is something seriously
wrong with over voltage, which you are not telling us about. Maybe an
interrupt storm? If there is something broken here, this patch needs
to be back ported to stable.
Andrew
next prev parent reply other threads:[~2021-09-10 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 19:09 [PATCH] net: phy: dp83tc811: modify list of interrupts enabled at initialization hnagalla
2021-09-02 23:23 ` Andrew Lunn
2021-09-06 20:51 ` [EXTERNAL] " Modi, Geet
2021-09-07 14:02 ` Andrew Lunn
[not found] ` <E61A9519-DBA6-4931-A2A0-78856819C362@ti.com>
2021-09-09 20:37 ` [EXTERNAL] " Andrew Lunn
2021-09-10 0:41 ` [EXTERNAL] " Modi, Geet
2021-09-10 1:30 ` Andrew Lunn [this message]
2021-09-10 1:42 ` [EXTERNAL] " Modi, Geet
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=YTq1SATpNvwo+ojg@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=geet.modi@ti.com \
--cc=hnagalla@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vikram.sharma@ti.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 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).