linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <RaghuramChary.Jallipalli@microchip.com>
To: <Jisheng.Zhang@synaptics.com>, <Woojung.Huh@microchip.com>,
	<UNGLinuxDriver@microchip.com>, <davem@davemloft.net>,
	<netdev@vger.kernel.org>, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] net: lan78xx: fix "enabled interrupts" warninig
Date: Mon, 8 Apr 2019 07:46:03 +0000	[thread overview]
Message-ID: <BL0PR11MB33292EC33542F7D4FE5208469F2C0@BL0PR11MB3329.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20190408140301.3dcbccdd@xhacker.debian>

> 
> Per my understanding, the proper handling of PHY irq is to make use of
> PHY_IGNORE_INTERRUPT then call phy_mac_interrupt when
> INT_ENP_PHY_INT is triggered.
> 

Hi Jisheng,
Thanks for the changes.
Is this warning specific to any linux version? Why do you think PHY irq domain handling is not proper? Maybe we can fix that rather removing complete IRQ domain code changes. 
Also, Can you pls let us know how this changes fixed your warning.

Thanks
-Raghu


  reply	other threads:[~2019-04-08  7:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08  6:10 [PATCH] net: lan78xx: fix "enabled interrupts" warninig Jisheng Zhang
2019-04-08  7:46 ` RaghuramChary.Jallipalli [this message]
2019-04-08  8:07   ` Jisheng Zhang
2019-04-08 10:46     ` RaghuramChary.Jallipalli
2019-04-09  1:36       ` Jisheng Zhang
2019-04-09  5:26         ` RaghuramChary.Jallipalli
2019-04-10  9:20         ` RaghuramChary.Jallipalli
2019-04-10  9:53           ` Jisheng Zhang
2019-04-10 10:27             ` Marc Zyngier
2019-04-17  3:49             ` RaghuramChary.Jallipalli
2019-04-17  8:22               ` Jisheng Zhang
2019-04-22  5:32                 ` RaghuramChary.Jallipalli

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=BL0PR11MB33292EC33542F7D4FE5208469F2C0@BL0PR11MB3329.namprd11.prod.outlook.com \
    --to=raghuramchary.jallipalli@microchip.com \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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 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).