All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Olaf Hering <olaf@aepfle.de>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v1] Increase framebuffer size to todays standards
Date: Wed, 28 Nov 2018 03:23:03 -0700	[thread overview]
Message-ID: <5BFE6C870200007800200ACB@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <1ed88038-161f-d2c2-a92f-2a89ad948801@arm.com>

>>> On 27.11.18 at 19:17, <julien.grall@arm.com> wrote:
> I would be surprised if someone ever used the HDLCD driver after it was 
> merged. I am not even sure if it even works.
> 
> Furthermore, this driver only targets development platform (i.g Juno) or 
> the models were pretty much everyone tends to use serial console for Xen.
> 
> So I would not worry if you break the support when backporting. I am 
> also happy to see it completely removed in old Xen version.

Thanks - I'll keep this in mind when backporting the eventual final
patch here. I'll probably remove the driver only in case the build
for it would fail with the change discussed here, which I don't
expect to be the case.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2018-11-28 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 19:14 [PATCH v1] Increase framebuffer size to todays standards Olaf Hering
2018-11-26 10:31 ` Jan Beulich
2018-11-26 16:03   ` Olaf Hering
2018-11-26 16:15     ` Jan Beulich
2018-11-27  9:26       ` Julien Grall
2018-11-27  9:44         ` Jan Beulich
2018-11-27 18:17           ` Julien Grall
2018-11-28 10:23             ` Jan Beulich [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=5BFE6C870200007800200ACB@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=olaf@aepfle.de \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.