[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160406185637.GA5168@vkoul-mobl.iind.intel.com>
Date: Wed, 6 Apr 2016 11:56:38 -0700
From: Vinod Koul <vinod.koul@...el.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Viresh Kumar <vireshk@...nel.org>, linux-kernel@...r.kernel.org,
dmaengine@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Hans-Christian Egtvedt <egtvedt@...fundet.no>,
Tejun Heo <tj@...nel.org>, Mark Brown <broonie@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mark Rutland <mark.rutland@....com>,
Vineet Gupta <vgupta@...opsys.com>, stable@...r.kernel.org
Subject: Re: [PATCH v3 01/15] dmaengine: dw: fix master selection
On Mon, Apr 04, 2016 at 08:10:54PM +0300, Andy Shevchenko wrote:
> On Mon, 2016-04-04 at 10:03 -0700, Vinod Koul wrote:
> > On Fri, Mar 18, 2016 at 04:24:40PM +0200, Andy Shevchenko wrote:
> > >
> > > + /*
> > > + * We need controller-specific data to set up slave
> > > transfers.
> > > + */
> > > + BUG_ON(chan->private && !dw_dma_filter(chan, chan-
> > > >private));
> > I don't think BUG_ON is apt here, gracefully failing and printing
> > that can
> > be better..
>
> Hm, this is coming from the existing code.
>
> I would prefer to keep this one as is since it's targeted to stable@,
> and I may issue sequential patch to replace BUG_ON. Sounds okay?
But since this is going stable, how about we remove here in the patch and
benefit stable tree as well?
Thanks
--
~Vinod
Powered by blists - more mailing lists