[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170208155947.GE30741@oracle.com>
Date: Wed, 8 Feb 2017 07:59:47 -0800
From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
To: Shannon Nelson <shannon.nelson@...cle.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net,
sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 net-next 6/9] sunvnet: straighten up message event
handling logic
On (02/07/17 14:12), Shannon Nelson wrote:
> +
> + /* we don't expect any other bits */
> + BUG_ON(port->rx_event & ~(LDC_EVENT_DATA_READY |
> + LDC_EVENT_RESET |
> + LDC_EVENT_UP));
> +
> + /* RESET takes precedent over any other event */
> + if (port->rx_event & LDC_EVENT_RESET) {
:
> port->rx_event = 0;
> return 0;
> }
> + if (port->rx_event & LDC_EVENT_UP) {
> + vio_link_state_change(vio, LDC_EVENT_UP);
> + port->rx_event = 0;
> + return 0;
> + }
>
> err = 0;
> tx_wakeup = 0;
IIRC there were timing-related situations where you can get woken up with
both UP and DATA_READY, and if my reading of your patch is
correct, we would ignore the DATA_READY, and return, right?
--Sowmini
Powered by blists - more mailing lists