From: Vinod Koul <vkoul@kernel.org>
To: "Ardelean, Alexandru" <Alex.Ardelean@analog.com>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: [1/2] dma: axi-dmac: don't check the number of frames for alignment
Date: Tue, 26 Feb 2019 13:31:25 +0530 [thread overview]
Message-ID: <20190226080125.GO31146@vkoul-mobl> (raw)
On 26-02-19, 07:14, Ardelean, Alexandru wrote:
> On Mon, 2019-02-25 at 12:22 +0530, Vinod Koul wrote:
> > [External]
> >
> >
> > On 15-02-19, 11:17, Alexandru Ardelean wrote:
> > > Fixes commit 0e3b67b348b8 ("dmaengine: Add support for the Analog
> > > Devices
> > > AXI-DMAC DMA controller")
> >
> > Do you mean to add a Fixes tag?
>
> Yep.
> I'm terrible at this apparently. I'll read about how to do that properly.
> Other maintainers have complained about this as well [i.e. the fact that I
> didn't add proper Fixes tags ].
So if it fixes a bug in original commit and should go immediately to
next rc-X then fixes is mostly appropriate.. (also backporting to
stable). In this case it doesnt seem so.
Also canonical form is
Fixes: abcdef : ("buggy patch")
and this line should be before the s-o-b line..
> >
> > > For 2D transfers, there is no requirement for Y_LENGTH to be aligned
> > > to the bus-width (or anything). X_LENGTH is required to be aligned
> > > though.
> > >
> > > So, we shouldn't check that the number of frames is aligned.
> >
> > Does this fix a bug as indicated by Fixes tag?
>
> Yes
well if it is aligned it shouldn't cause break right. Yes not having
aligned helps the driver but seems to be correct the wrong
interpretation/implementation.. right?
next reply other threads:[~2019-02-26 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 8:01 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-26 8:36 [1/2] dma: axi-dmac: don't check the number of frames for alignment Ardelean, Alexandru
2019-02-26 7:14 Ardelean, Alexandru
2019-02-25 6:52 Vinod Koul
2019-02-15 9:17 Alexandru Ardelean
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=20190226080125.GO31146@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=Alex.Ardelean@analog.com \
--cc=dmaengine@vger.kernel.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