linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Dan Carpenter <dan.carpenter@oracle.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the cifs tree
Date: Thu, 6 Aug 2020 10:31:33 -0500	[thread overview]
Message-ID: <CAH2r5mvGD3ftLDfwrpx61kaJQnPpspupdDHD8NOjnF-q-ByTfg@mail.gmail.com> (raw)
In-Reply-To: <20200806164505.0eada105@canb.auug.org.au>

Dan,
I just fixed the Author tag in this patch to match your email address
but seems like the author email address gets mangled when sent through
some mailing lists.  Any ideas how to avoid this.

On Thu, Aug 6, 2020 at 1:45 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Commit
>
>   2676d210d2f4 ("cifs: Fix an error pointer dereference in cifs_mount()")
>
> is missing a Signed-off-by from its author.
>
> This is only pisked up by my script because of the mangling of the email
> sender address by the mailing list it passed through.  I guess a little
> more care is required to make sure the author attribution is correct in
> this case.
>
> --
> Cheers,
> Stephen Rothwell



-- 
Thanks,

Steve

  reply	other threads:[~2020-08-06 16:52 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  6:45 linux-next: Signed-off-by missing for commit in the cifs tree Stephen Rothwell
2020-08-06 15:31 ` Steve French [this message]
2020-08-06 22:33   ` Stephen Rothwell
2020-08-07 11:49     ` Dan Carpenter
  -- strict thread matches above, loose matches on Subject: below --
2024-01-28  3:56 Stephen Rothwell
2024-01-28 12:38 ` Steve French
2023-09-19 21:06 Stephen Rothwell
2023-09-20  3:04 ` Steve French
2023-06-19 22:30 Stephen Rothwell
2023-06-19 23:17 ` Steve French
2023-02-23 21:10 Stephen Rothwell
2023-02-23 22:43 ` Steve French
2022-10-18  3:38 Stephen Rothwell
2022-10-18  3:45 ` Steve French
2022-08-24  6:39 Stephen Rothwell
2022-08-24 14:35 ` Steve French
2022-08-17 22:21 Stephen Rothwell
2022-08-17 23:07 ` Steve French
2022-06-22 23:21 Stephen Rothwell
2022-06-22 23:39 ` Steve French
2022-06-16 22:34 Stephen Rothwell
2022-06-16 22:41 ` Steve French
2022-05-25 22:24 Stephen Rothwell
2022-05-25 22:37 ` Steve French
2021-04-08 12:07 Stephen Rothwell
2021-04-08 16:09 ` Steve French
2021-03-26  9:06 Stephen Rothwell
2021-02-16 11:33 Stephen Rothwell
2021-02-03 10:59 Stephen Rothwell
2021-02-03 15:41 ` Steve French
2020-12-18  5:57 Stephen Rothwell
2020-12-18  6:04 ` Steve French
2020-12-14 19:32 Stephen Rothwell
2020-12-14 19:42 ` Steve French
2020-12-13 10:14 Stephen Rothwell
2020-12-13 16:10 ` Steve French
2020-12-10 10:45 Stephen Rothwell
2020-12-10 19:06 ` Steve French
2020-09-29 22:31 Stephen Rothwell
2020-09-29 22:42 ` Steve French
2020-03-29 21:57 Stephen Rothwell
2020-03-29 22:00 ` Steve French
2020-03-09 22:28 Stephen Rothwell
2020-03-09 23:07 ` Steve French
2020-02-24 20:52 Stephen Rothwell
2020-02-24 22:27 ` Steve French
2020-01-27 19:57 Stephen Rothwell
2020-01-28 17:47 ` Steve French
2020-01-19  1:22 Stephen Rothwell
2020-01-19  3:02 ` Steve French
2019-11-14 20:10 Stephen Rothwell
2019-11-14 21:48 ` Steve French
2019-08-01 21:54 Stephen Rothwell
2019-08-01 22:42 ` Steve French
2019-06-25 11:08 Stephen Rothwell
2019-06-25 17:19 ` Steve French
2019-05-07 21:32 Stephen Rothwell
2019-05-08  4:03 ` Steve French
2019-04-02 20:40 Stephen Rothwell
2019-04-03  4:27 ` Steve French
2019-03-21 18:47 Stephen Rothwell
2019-03-21 19:00 ` Steve French
2019-02-14  7:37 Stephen Rothwell
2018-12-24 11:45 Stephen Rothwell
2018-12-24 16:10 ` Steve French
2018-11-05  5:55 Stephen Rothwell
2018-08-21  4:18 Stephen Rothwell
2018-08-21  4:20 ` Steve French
2018-08-01 10:58 Stephen Rothwell
2018-08-01 16:58 ` Steve French
2018-04-01  1:38 Stephen Rothwell
2018-04-01  4:45 ` Steve French
2017-09-20  4:28 Stephen Rothwell
2017-09-04 21:56 Stephen Rothwell
     [not found] ` <CAH2r5mtGthm6XkatxGMUdJwc9CXgdo31xgPLZuRxWqXgL1g19Q@mail.gmail.com>
     [not found]   ` <CAH2r5mtGthm6XkatxGMUdJwc9CXgdo31xgPLZuRxWqXgL1g19Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-05  1:58     ` Steve French

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=CAH2r5mvGD3ftLDfwrpx61kaJQnPpspupdDHD8NOjnF-q-ByTfg@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-cifs@vger.kernel.org \
    --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).