Received: by 10.192.165.148 with SMTP id m20csp283185imm; Tue, 24 Apr 2018 22:32:26 -0700 (PDT) X-Google-Smtp-Source: AIpwx48quSYZxcNUAKM3wrV/H8KmW2xd7uvUZcWMfKCAXEPzNF133y2h4XUKhh4rkrCFvymDSqy1 X-Received: by 10.99.127.87 with SMTP id p23mr22526220pgn.240.1524634346082; Tue, 24 Apr 2018 22:32:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524634346; cv=none; d=google.com; s=arc-20160816; b=Vr4gJPyASNZ2YHnl0iDMZw/V+OTdShbG6st1Ei7SVOtQ0cMQqHcIHnoniR4k7cKE4c RRE1OBqlpZ8fuXUOTf1pNAM2JP6zZqLSwjLHIWkI27oFVeEF/eJovRCUrMh42P7mgzxZ hfivIstfQ9CdcLMOpuMurAv5Q7dhaCp0Ddsw3rXf8I5skE9wVak8LmKK5Fprhn0mz3CU Ft7l9UtC9P0f72e0/L2PjWMfvhPW+acSp+ROEbo02GkiXW1GvR2eA5G+8UzXRmBDgQoo D1G/1tTOrscWv0BBzDTdvSzbc2WOQT/4I0r3DMXJt3DNdcN1wIZakgjfGWA98Pw9NEQk 6PEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:date:cc:to:from:subject :message-id:arc-authentication-results; bh=enAbHCiFz9OeE20Vl+XoaP0idIws7D5fq6tzGLiDvZM=; b=h6vupJJ+YrieWpgXy+vifstTMQrGpxa+2f3tTi83DnBrvsdxbv8ogrnVrZIuHMzdmH b8vH6vwSz7W4GewsNHCTmAfWrDuHNFrOk57weVg6mvcn0u6VI1EPJWm70KzthBkODVZp oAmD8ZOjfoEYtOo/rMFniUjTS8Z5q0g1UcoIlUz/RH3mBRf3kZW8pVVBtlLw/rV/XGar XSQ8Kj/RBaPjzCaVH+DqJdpI7D269+JF9aHaA6P0gnCPtcfA5MjO6ewR+NHeb9rZG7+x tV10SM5OPq2mU8djcTjGpTlGsgM1HzzSJN8IQQ57IFJynoTgI9tNkEls+srC5ZiV/QjA BeqQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s3-v6si14615037plp.185.2018.04.24.22.32.11; Tue, 24 Apr 2018 22:32:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751269AbeDYFbH (ORCPT + 99 others); Wed, 25 Apr 2018 01:31:07 -0400 Received: from mga14.intel.com ([192.55.52.115]:5265 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750921AbeDYFbE (ORCPT ); Wed, 25 Apr 2018 01:31:04 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Apr 2018 22:31:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,325,1520924400"; d="scan'208";a="223128493" Received: from tmuluk-mobl4.ger.corp.intel.com ([10.249.254.131]) by fmsmga005.fm.intel.com with ESMTP; 24 Apr 2018 22:31:01 -0700 Message-ID: Subject: Re: linux-next: Signed-off-by missing for commit in the wireless-drivers-next tree From: Luciano Coelho To: Stephen Rothwell , Kalle Valo , Wireless Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Gregory Greenman , Sara Sharon Date: Wed, 25 Apr 2018 08:31:00 +0300 In-Reply-To: <20180425105619.09f58e39@canb.auug.org.au> References: <20180425105619.09f58e39@canb.auug.org.au> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.1-2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.