From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vinod Koul <vkoul@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the dmaengine tree
Date: Fri, 30 Aug 2024 14:47:46 +1000 [thread overview]
Message-ID: <20240830144746.58b98a53@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
Hi all,
The following commits are also in the dmaengine-fixes tree as different
commits (but the same patches):
3f92ee7c4a4e ("dmaengine: dw: Unify ret-val local variables naming")
17d4353413a4 ("dmaengine: dw: Simplify max-burst calculation procedure")
2f87a9671ed5 ("dmaengine: dw: Define encode_maxburst() above prepare_ctllo() callbacks")
d34e8466c633 ("dmaengine: dw: Simplify prepare CTL_LO methods")
5bb11aedb530 ("dmaengine: dw: Add memory bus width verification")
e2c97d200ac3 ("dmaengine: dw: Add peripheral bus width verification")
These are commits
2ebc36b9581d ("dmaengine: dw: Unify ret-val local variables naming")
d8fa0802f635 ("dmaengine: dw: Simplify max-burst calculation procedure")
3acb301d3374 ("dmaengine: dw: Define encode_maxburst() above prepare_ctllo() callbacks")
1fd6fe89055e ("dmaengine: dw: Simplify prepare CTL_LO methods")
d04b21bfa1c5 ("dmaengine: dw: Add memory bus width verification")
b336268dde75 ("dmaengine: dw: Add peripheral bus width verification")
in the dmaengine-fixes tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-08-30 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 4:47 Stephen Rothwell [this message]
2024-08-30 7:24 ` linux-next: duplicate patches in the dmaengine tree Vinod Koul
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=20240830144746.58b98a53@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=vkoul@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