From: Richard Weinberger <richard@nod•at>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Artem Bityutskiy <dedekind1@gmail•com>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
linux-kernel <linux-kernel@vger•kernel.org>,
Quanyang Wang <quanyang.wang@windriver•com>
Subject: Re: linux-next: Fixes tag needs some work in the ubifs tree
Date: Sun, 19 Jan 2020 23:17:56 +0100 (CET) [thread overview]
Message-ID: <1034266714.24281.1579472276843.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20200120091239.045c7c65@canb.auug.org.au>
----- Ursprüngliche Mail -----
> Von: "Stephen Rothwell" <sfr@canb•auug.org.au>
> An: "Artem Bityutskiy" <dedekind1@gmail•com>
> CC: "Linux Next Mailing List" <linux-next@vger•kernel.org>, "linux-kernel" <linux-kernel@vger•kernel.org>, "Quanyang
> Wang" <quanyang.wang@windriver•com>, "richard" <richard@nod•at>
> Gesendet: Sonntag, 19. Januar 2020 23:12:39
> Betreff: linux-next: Fixes tag needs some work in the ubifs tree
> Hi all,
>
> In commit
>
> 31f36312d2ca ("ubifs: fix memory leak from c->sup_node")
>
> Fixes tag
>
> Fixes: 4793e7c5e1c8 ("ubifs: Store read superblock node")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
>
> Did you meean
>
> Fixes: 4793e7c5e1c8 ("UBIFS: add bulk-read facility")
>
> or
>
> Fixes: fd6150051bec ("ubifs: Store read superblock node")
That should be fd6150051bec ("ubifs: Store read superblock node").
/me fixes. No idea how that happened.
Thanks,
//richard
next prev parent reply other threads:[~2020-01-19 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 22:12 linux-next: Fixes tag needs some work in the ubifs tree Stephen Rothwell
2020-01-19 22:17 ` Richard Weinberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-17 7:09 Stephen Rothwell
2020-01-19 19:18 ` Richard Weinberger
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=1034266714.24281.1579472276843.JavaMail.zimbra@nod.at \
--to=richard@nod$(echo .)at \
--cc=dedekind1@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=quanyang.wang@windriver$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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