From: Matthew Wilcox <willy@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christian Brauner <brauner@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the vfs-brauner tree
Date: Thu, 8 Aug 2024 01:16:33 +0100 [thread overview]
Message-ID: <ZrQOYVldGlkymDrG@casper.infradead.org> (raw)
In-Reply-To: <20240808082706.687536aa@canb.auug.org.au>
On Thu, Aug 08, 2024 at 08:27:06AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> a60b0e8f150f ("ufs: Convert ufs_check_page() to ufs_check_folio()")
>
> is missing a Signed-off-by from its author.
Indeed; my fault. Guess I forgot to add "-s" at some point.
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
next prev parent reply other threads:[~2024-08-08 0:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 22:27 linux-next: Signed-off-by missing for commit in the vfs-brauner tree Stephen Rothwell
2024-08-08 0:16 ` Matthew Wilcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 10:11 Stephen Rothwell
2025-07-16 22:21 Stephen Rothwell
2025-04-13 22:23 Stephen Rothwell
2025-04-14 11:04 ` Christian Brauner
2024-09-08 21:47 Stephen Rothwell
2024-09-09 10:28 ` Christian Brauner
2024-07-31 22:05 Stephen Rothwell
2024-08-01 7:01 ` Christian Brauner
2024-07-31 22:03 Stephen Rothwell
2024-08-01 7:01 ` Christian Brauner
2024-07-30 13:05 Stephen Rothwell
2024-07-30 14:22 ` Christian Brauner
2024-05-08 22:19 Stephen Rothwell
2024-05-10 8:52 ` Christian Brauner
2023-12-03 22:01 Stephen Rothwell
2023-12-03 22:40 ` Lukas Schauer
2023-12-05 11:19 ` Christian Brauner
2023-05-23 22:18 Stephen Rothwell
2023-05-24 9:10 ` Christian Brauner
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=ZrQOYVldGlkymDrG@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@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