All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: 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: Wed, 25 May 2022 07:07:23 +1000	[thread overview]
Message-ID: <20220525070723.426cbfd4@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]

Hi all,

Commits

  5db490f54497 ("dt-bindings: PCI: qcom: Add schema for sc7280 chipset")
  ee485c61f0e5 ("dt-bindings: PCI: qcom: Specify reg-names explicitly")
  3d49f91acbcc ("dt-bindings: PCI: qcom: Do not require resets on msm8996 platforms")
  e93dde4b6768 ("dt-bindings: PCI: qcom: Convert to YAML")
  ed5e8fe0db30 ("PCI: qcom: Fix unbalanced PHY init on probe errors")
  f36120778857 ("PCI: qcom: Fix runtime PM imbalance on probe errors")
  53063d1437e5 ("PCI: qcom: Fix pipe clock imbalance")
  5945b7056322 ("PCI: qcom: Add SM8150 SoC support")
  ddd0cc4df5a1 ("dt-bindings: pci: qcom: Document PCIe bindings for SM8150 SoC")

are missing a Signed-off-by from their committer.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-05-24 21:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 21:07 Stephen Rothwell [this message]
2022-05-24 21:43 ` linux-next: Signed-off-by missing for commit in the pci tree Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2025-06-01  8:27 Stephen Rothwell
2025-01-21 20:47 Stephen Rothwell
2025-01-21 23:37 ` Bjorn Helgaas
2024-07-08  8:15 Stephen Rothwell
2024-07-09  3:31 ` Krzysztof Wilczyński
2024-07-03  0:45 Stephen Rothwell
2024-07-03  0:59 ` Krzysztof Wilczyński
2023-10-05 22:05 Stephen Rothwell
2023-10-05 22:23 ` Bjorn Helgaas
2023-09-17 21:57 Stephen Rothwell
2023-02-10  4:38 Stephen Rothwell
2023-02-10 23:28 ` 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=20220525070723.426cbfd4@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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.