linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the pci tree
Date: Tue, 24 May 2022 16:43:56 -0500	[thread overview]
Message-ID: <20220524214356.GA275586@bhelgaas> (raw)
In-Reply-To: <20220525070723.426cbfd4@canb.auug.org.au>

On Wed, May 25, 2022 at 07:07:23AM +1000, Stephen Rothwell wrote:
> 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.

Sorry, fixed.

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

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 21:07 linux-next: Signed-off-by missing for commit in the pci tree Stephen Rothwell
2022-05-24 21:43 ` Bjorn Helgaas [this message]
  -- 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
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=20220524214356.GA275586@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).