From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dmaengine: at_xdmac: lock fixes
Date: Thu, 4 Jun 2015 21:22:01 +0530 [thread overview]
Message-ID: <20150604155201.GP3140@localhost> (raw)
In-Reply-To: <20150604150946.GA17733@odux.rfo.atmel.com>
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
prev parent reply other threads:[~2015-06-04 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:52 [PATCH 1/2] dmaengine: at_xdmac: lock fixes Ludovic Desroches
2015-06-03 14:52 ` [PATCH 2/2] dmaengine: at_xdmac: rework slave configuration part Ludovic Desroches
2015-06-04 7:43 ` Nicolas Ferre
2015-06-04 7:37 ` [PATCH 1/2] dmaengine: at_xdmac: lock fixes Nicolas Ferre
2015-06-04 14:19 ` Vinod Koul
2015-06-04 15:09 ` Ludovic Desroches
2015-06-04 15:52 ` Vinod Koul [this message]
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=20150604155201.GP3140@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).