From: Steve French <smfrench@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: CIFS <linux-cifs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the cifs tree
Date: Tue, 30 Aug 2022 17:10:47 -0500 [thread overview]
Message-ID: <CAH2r5muWkiYDNXUibC6RR9s0rTYda2zDGpJhTpnpG7PMBXhh-Q@mail.gmail.com> (raw)
In-Reply-To: <20220831074247.5ae119a3@canb.auug.org.au>
sorry about the cut-n-paste error
fixed
On Tue, Aug 30, 2022 at 4:42 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> ebcc8ccc13e0 ("smb3: use filemap_write_and_wait_range instead of filemap_write_and_wait")
>
> Fixes tag
>
> Fixes: c3a72bb21320 ("Reviewed-by: David Howells <dhowells@redhat.com>")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
>
> So,
>
> Fixes: c3a72bb21320 ("smb3: Move the flush out of smb2_copychunk_range() into its callers")
>
> --
> Cheers,
> Stephen Rothwell
--
Thanks,
Steve
next prev parent reply other threads:[~2022-08-30 22:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 21:42 linux-next: Fixes tag needs some work in the cifs tree Stephen Rothwell
2022-08-30 22:10 ` Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 21:09 Stephen Rothwell
2023-02-23 21:27 ` David Howells
2023-02-23 22:43 ` Steve French
2022-11-15 20:41 Stephen Rothwell
2022-11-16 6:22 ` Steve French
2022-10-15 8:57 Stephen Rothwell
2022-10-15 15:06 ` Steve French
2022-10-05 23:30 Stephen Rothwell
2022-10-06 2:18 ` Steve French
2022-08-24 6:37 Stephen Rothwell
2022-08-24 14:23 ` Steve French
2022-07-05 22:06 Stephen Rothwell
2021-05-19 21:53 Stephen Rothwell
2021-05-20 0:21 ` Steve French
2019-05-24 4:27 Stephen Rothwell
2019-05-24 14:14 ` Steve French
2019-05-29 3:24 ` Murphy Zhou
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=CAH2r5muWkiYDNXUibC6RR9s0rTYda2zDGpJhTpnpG7PMBXhh-Q@mail.gmail.com \
--to=smfrench@gmail.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).