From: Finn Thain <fthain@telegraphics.com.au>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: linux-fbdev@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Paul Burton <paulburton@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
James Hogan <jhogan@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
Thomas Bogendoerfer <tbogendoerfer@suse.de>,
dri-devel@lists.freedesktop.org,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH 1/3] fbdev/g364fb: Fix build failure
Date: Wed, 05 Feb 2020 22:18:21 +0000 [thread overview]
Message-ID: <alpine.LNX.2.22.394.2002060918030.8@nippy.intranet> (raw)
In-Reply-To: <08447d52-0007-6f68-3848-209295a61d13@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
On Wed, 5 Feb 2020, Philippe Mathieu-Daudé wrote:
> Note, you need to rebase your series due to:
>
> commit 8a48ac339398f21282985bff16552447d41dcfb2
> Author: Jani Nikula <jani.nikula@intel.com>
> Date: Tue Dec 3 18:38:50 2019 +0200
>
> video: constify fb ops across all drivers
>
OK.
Thanks for your review.
next prev parent reply other threads:[~2020-02-05 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 2:33 [PATCH 0/3] Improve MIPS Magnum support Finn Thain
2020-02-02 2:33 ` [PATCH 1/3] fbdev/g364fb: Fix build failure Finn Thain
2020-02-05 18:02 ` Philippe Mathieu-Daudé
2020-02-05 18:19 ` Philippe Mathieu-Daudé
2020-02-05 22:18 ` Finn Thain [this message]
2020-02-05 22:17 ` Finn Thain
2020-02-06 23:00 ` Philippe Mathieu-Daudé
2020-02-07 0:10 ` Finn Thain
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=alpine.LNX.2.22.394.2002060918030.8@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=f4bug@amsat.org \
--cc=jhogan@kernel.org \
--cc=laurent@vivier.eu \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=tbogendoerfer@suse.de \
--cc=tsbogend@alpha.franken.de \
/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).