From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the pci tree
Date: Fri, 10 Feb 2023 15:38:34 +1100 [thread overview]
Message-ID: <20230210153834.0452f24d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
Hi all,
Commits
da006a8c9352 ("dmaengine: dw-edma: Use non-atomic io-64 methods")
e3042508ac7c ("dmaengine: dw-edma: Fix readq_ch() return value truncation")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-02-10 4:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 4:38 Stephen Rothwell [this message]
2023-02-10 23:28 ` linux-next: Signed-off-by missing for commit in the pci tree Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2023-10-05 22:05 Stephen Rothwell
2023-10-05 22:23 ` Bjorn Helgaas
2023-09-17 21:57 Stephen Rothwell
2022-05-24 21:07 Stephen Rothwell
2022-05-24 21:43 ` Bjorn Helgaas
2021-02-24 20:21 Stephen Rothwell
2021-02-24 21:31 ` Bjorn Helgaas
2021-01-20 7:25 Stephen Rothwell
2021-01-20 19:26 ` Bjorn Helgaas
2019-08-20 21:19 Stephen Rothwell
2019-08-21 9:02 ` Lorenzo Pieralisi
2019-09-09 23:10 ` Haiyang Zhang
2019-09-10 11:17 ` Lorenzo Pieralisi
2019-09-10 13:56 ` Haiyang Zhang
2019-02-27 21:01 Stephen Rothwell
2019-02-27 23:51 ` Bjorn Helgaas
2019-02-28 10:03 ` Lorenzo Pieralisi
2019-02-11 23:10 Stephen Rothwell
2019-02-11 23:58 ` Bjorn Helgaas
2018-04-01 1:41 Stephen Rothwell
2018-04-02 0:19 ` Bjorn Helgaas
2018-03-03 4:44 Stephen Rothwell
2018-03-05 14:10 ` Bjorn Helgaas
2018-01-17 20:53 Stephen Rothwell
2018-01-17 21:00 ` Bjorn Helgaas
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=20230210153834.0452f24d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lpieralisi@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;
as well as URLs for NNTP newsgroup(s).