From: Luciano Coelho <luciano.coelho@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Kalle Valo <kvalo@codeaurora.org>,
Wireless <linux-wireless@vger.kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gregory Greenman <gregory.greenman@intel.com>,
Sara Sharon <sara.sharon@intel.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the wireless-drivers-next tree
Date: Wed, 25 Apr 2018 08:31:00 +0300 [thread overview]
Message-ID: <ef221a8abfecadfcbc637a0731150e648c85315f.camel@intel.com> (raw)
In-Reply-To: <20180425105619.09f58e39@canb.auug.org.au>
Hi,
On Wed, 2018-04-25 at 10:56 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 84226ca1c5d3 ("iwlwifi: mvm: support offload of AMSDU rate
> control")
>
> is missing a Signed-off-by from its author.
I checked this and it should be fine. The author is actually wrong in
the commit. Sara is the actual author and we have her S-o-B in the
commit.
I have no idea how Gregory became the author in that commit, though. I
checked exactly how I committed it and checked the author in our
internal tree. It's all fine, but for some really weird reason that I
can't figure out, Gregory became the author of the commit when I
applied that patch. The AuthorDate is also wrong. I checked my bash
history to see how I applied the patch and everything looks normal...
*confused*
--
Cheers,
Luca.
next prev parent reply other threads:[~2018-04-25 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 0:56 linux-next: Signed-off-by missing for commit in the wireless-drivers-next tree Stephen Rothwell
2018-04-25 0:56 ` Stephen Rothwell
2018-04-25 5:31 ` Luciano Coelho [this message]
2019-02-10 20:28 Stephen Rothwell
2019-02-11 6:12 ` Kalle Valo
2019-02-11 6:12 ` Kalle Valo
2020-05-18 13:03 Stephen Rothwell
2020-05-19 8:52 ` Kalle Valo
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=ef221a8abfecadfcbc637a0731150e648c85315f.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=gregory.greenman@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sara.sharon@intel.com \
--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 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.