linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wireless <linux-wireless@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Govind Singh <govinds@codeaurora.org>,
	ath10k@lists.infradead.org
Subject: Re: linux-next: Signed-off-by missing for commit in the wireless-drivers-next tree
Date: Mon, 11 Feb 2019 08:12:52 +0200	[thread overview]
Message-ID: <87lg2m7t0b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20190211072814.7428f192@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 11 Feb 2019 07:28:14 +1100")

+ ath10k

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi all,
>
> Commit
>
>   768ec4c012ac ("ath10k: update HOST capability qmi message")
>
> is missing a Signed-off-by from its author.

Oh, I had missed that. Thanks for reporting.

Unfortunately it would be difficult to rebase wireless-drivers-next so I
can't (easily) fix this. But v1 had s-o-b so at least we have the sign
off publically available:

https://patchwork.kernel.org/patch/10688563/

-- 
Kalle Valo

  reply	other threads:[~2019-02-11  6:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-10 20:28 linux-next: Signed-off-by missing for commit in the wireless-drivers-next tree Stephen Rothwell
2019-02-11  6:12 ` Kalle Valo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-18 13:03 Stephen Rothwell
2020-05-19  8:52 ` Kalle Valo
2018-04-25  0:56 Stephen Rothwell
2018-04-25  5:31 ` Luciano Coelho

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=87lg2m7t0b.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=govinds@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@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).