linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ritesh Harjani <riteshh@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, "Theodore Ts'o" <tytso@mit.edu>
Cc: 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 ext4 tree
Date: Tue, 2 Jun 2020 08:37:09 +0530	[thread overview]
Message-ID: <20200602030709.E9DBAA4040@d06av23.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20200529221128.668844ca@canb.auug.org.au>



On 5/29/20 5:41 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Commit
> 
>    560d6b3da024 ("ext4: mballoc: fix possible NULL ptr & remove BUG_ONs from DOUBLE_CHECK")
> 
> is missing a Signed-off-by from its author.

My bad. I guess it got missed due to the three dotted lines.

https://patchwork.ozlabs.org/project/linux-ext4/patch/9a54f8a696ff17c057cd571be3d15ac3ec1407f1.1589086800.git.riteshh@linux.ibm.com/

-ritesh

  reply	other threads:[~2020-06-02  3:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 12:11 linux-next: Signed-off-by missing for commit in the ext4 tree Stephen Rothwell
2020-06-02  3:07 ` Ritesh Harjani [this message]
2020-06-02  3:22   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-09-11  7:07 Stephen Rothwell
2023-06-15  5:24 Stephen Rothwell
2023-02-19 20:33 Stephen Rothwell
2022-10-03 20:16 Stephen Rothwell
2022-05-19 22:42 Stephen Rothwell
2021-07-05 22:11 Stephen Rothwell
2020-08-06 21:53 Stephen Rothwell
2019-09-04 21:39 Stephen Rothwell
2019-04-30 22:06 Stephen Rothwell
2019-05-01  2:01 ` Theodore Ts'o
2019-04-25 21:05 Stephen Rothwell
2018-08-01 21:37 Stephen Rothwell
2017-12-17 20:46 Stephen Rothwell
2017-08-25  0:01 Stephen Rothwell

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=20200602030709.E9DBAA4040@d06av23.portsmouth.uk.ibm.com \
    --to=riteshh@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tytso@mit.edu \
    /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).