From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the scmi tree
Date: Thu, 2 Jan 2020 11:15:10 +0000 [thread overview]
Message-ID: <20200102111510.GB4864@bogus> (raw)
In-Reply-To: <20200101173801.2e9a1758@canb.auug.org.au>
On Wed, Jan 01, 2020 at 05:38:01PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 75ee475c4018 ("drivers: firmware: scmi: Extend SCMI transport layer by trace events")
> 60542ecbce11 ("include: trace: Add SCMI header with trace events")
Thanks for the report, I noticed this before I sent PR to ARM SoC but
forgot to update for-linux-next branch, now fixed.
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-01-02 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 6:38 linux-next: Signed-off-by missing for commit in the scmi tree Stephen Rothwell
2020-01-02 11:15 ` Sudeep Holla [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-18 11:08 Stephen Rothwell
2020-05-18 11:13 ` Sudeep Holla
2020-05-18 15:56 ` André Przywara
2023-09-11 23:09 Stephen Rothwell
2023-09-12 9:57 ` Sudeep Holla
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=20200102111510.GB4864@bogus \
--to=sudeep.holla@arm.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