linux-kernel - Re: [PATCH 1/2] dmaengine: at

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150604155201.GP3140@localhost>
Date:	Thu, 4 Jun 2015 21:22:01 +0530
From:	Vinod Koul <vinod.koul@...el.com>
To:	linux-arm-kernel@...ts.infradead.org, dmaengine@...r.kernel.org,
	linux-kernel@...r.kernel.org, nicolas.ferre@...el.com,
	maxime.ripard@...e-electrons.com
Subject: Re: [PATCH 1/2] dmaengine: at_xdmac: lock fixes

On Thu, Jun 04, 2015 at 05:09:46PM +0200, Ludovic Desroches wrote:
> > > @@ -591,11 +592,13 @@ at_xdmac_prep_slave_sg(struct dma_chan *chan, struct scatterlist *sgl,
> > >  		       unsigned int sg_len, enum dma_transfer_direction direction,
> > >  		       unsigned long flags, void *context)
> > >  {
> > > -	struct at_xdmac_chan	*atchan = to_at_xdmac_chan(chan);
> > > -	struct at_xdmac_desc	*first = NULL, *prev = NULL;
> > > -	struct scatterlist	*sg;
> > > -	int			i;
> > > -	unsigned int		xfer_size = 0;
> > > +	struct at_xdmac_chan		*atchan = to_at_xdmac_chan(chan);
> > > +	struct at_xdmac_desc		*first = NULL, *prev = NULL;
> > > +	struct scatterlist		*sg;
> > > +	int				i;
> > > +	unsigned int			xfer_size = 0;
> > > +	unsigned long			irqflags;
> > > +	struct dma_async_tx_descriptor	*ret = NULL;
> > This doesnt comply with stable rules, and you should not keep this in fixes
> > either :(
> > 
> >   - It cannot contain any "trivial" fixes in it (spelling changes,
> >     whitespace cleanups, etc).
> 
> Ok I understand, so what is the way to manage this case? I did
> "whitespace cleanup" because of
> +   struct dma_async_tx_descriptor  *ret = NULL;
> which breaks previous indentation, so in my mind it was not cleanup.
> 
> Do I need to send you a patch to correct identation due to this fix or to send
> a specific patch for stable without identation change?
I think only adding the last line should do, in whatever indentation you
prefer

Later on if you want to align them to whatever alignment you prefer send a
follow on patch

Also on 2nd patch, it looks good, but was wondering if you could split it
up. This will help folks backporting the changes to stable as well

Thanks
-- 
~Vinod

--
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/