[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1347560357.5884.7.camel@joe2Laptop>
Date: Thu, 13 Sep 2012 11:19:17 -0700
From: Joe Perches <joe@...ches.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Samuel Iglesias Gonsalvez <siglesias@...lia.com>,
devel@...verdev.osuosl.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jens Taprogge <jens.taprogge@...rogge.org>,
linux-kernel@...r.kernel.org,
industrypack-devel@...ts.sourceforge.net
Subject: Re: [PATCH 07/24] Staging: ipack/devices/ipoctal: Store isr masks
in ipoctal_channel
On Thu, 2012-09-13 at 20:49 +0300, Dan Carpenter wrote:
> On Thu, Sep 13, 2012 at 08:43:12PM +0300, Dan Carpenter wrote:
> > On Wed, Sep 12, 2012 at 02:55:29PM +0200, Samuel Iglesias Gonsalvez wrote:
> > > From: Jens Taprogge <jens.taprogge@...rogge.org>
> > >
> > > This way interrupt handling becomes independent of the channel number.
> > >
> > > Signed-off-by: Jens Taprogge <jens.taprogge@...rogge.org>
> > > Signed-off-by: Samuel Iglesias Gonsalvez <siglesias@...lia.com>
> > > ---
> > > @@ -213,7 +206,7 @@ static int ipoctal_irq_handler(void *arg)
> > > }
> > >
> > > /* RX data */
> > > - if (isr_rx_rdy && (sr & SR_RX_READY)) {
> > > + if ((isr && channel->isr_rx_rdy_mask) && (sr & SR_RX_READY)) {
> > ^^
> > Bitwise AND intended here I think.
> >
>
> Never mind. It gets silently fixed in the next patch.
Nope, you were right the first time.
It shouldn't be silently fixed,
The best path is to rework the original patch
to fix the misuse or the worse path is that the
subsequent patch log should mention the fix.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists