From: Jiri Slaby <jslaby@suse.cz>
To: Ming Li <limingming.li@huawei.com>, b.zolnierkie@samsung.com
Cc: gregkh@linuxfoundation.org, john.wanghui@huawei.com,
cuibixuan@huawei.com, linux-next@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH -next] vc: Fix build errors
Date: Sat, 25 Jul 2020 09:41:53 +0200 [thread overview]
Message-ID: <98f7beee-8fab-6c56-7179-424b6bb45443@suse.cz> (raw)
In-Reply-To: <20200725074743.31740-1-limingming.li@huawei.com>
On 25. 07. 20, 9:47, Ming Li wrote:
> Build errors are seen on MIPS platforms because of
> vc state separation and the following build erros
> were reported.
Thanks, but already fixed:
https://lore.kernel.org/dri-devel/20200724062735.18229-1-jslaby@suse.cz/
--
js
suse labs
prev parent reply other threads:[~2020-07-25 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 7:47 [PATCH -next] vc: Fix build errors Ming Li
2020-07-25 7:41 ` Jiri Slaby [this message]
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=98f7beee-8fab-6c56-7179-424b6bb45443@suse.cz \
--to=jslaby@suse.cz \
--cc=b.zolnierkie@samsung.com \
--cc=cuibixuan@huawei.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.wanghui@huawei.com \
--cc=limingming.li@huawei.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).