From: Helge Deller <deller@gmx•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "Z. Liu" <liuzx@knownsec•com>,
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 fbdev tree
Date: Mon, 17 Jan 2022 22:41:07 +0100 [thread overview]
Message-ID: <c86bd360-a3d3-9aba-cd98-d1458b301787@gmx.de> (raw)
In-Reply-To: <20220118083336.25b0bcd6@canb.auug.org.au>
On 1/17/22 22:33, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> a274f635669a ("matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen")
>
> Fixes tag
>
> Fixes: 1be60bd66d54 ("matroxfb: add Matrox MGA-G200eW board support")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 11be60bd66d5 ("matroxfb: add Matrox MGA-G200eW board support")
Yes.
Fixed up now.
Thanks!
Helge
next prev parent reply other threads:[~2022-01-17 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 21:33 linux-next: Fixes tag needs some work in the fbdev tree Stephen Rothwell
2022-01-17 21:41 ` Helge Deller [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-10 20:24 Stephen Rothwell
2019-02-11 9:10 ` Michal Vokáč
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=c86bd360-a3d3-9aba-cd98-d1458b301787@gmx.de \
--to=deller@gmx$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=liuzx@knownsec$(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