From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: add screen_info for console support
Date: Tue, 20 Aug 2013 14:04:04 -0400 [thread overview]
Message-ID: <1377021844.3591.1.camel@t520.redhat.com> (raw)
In-Reply-To: <20130820171453.GF21383@arm.com>
On Tue, 2013-08-20 at 18:14 +0100, Catalin Marinas wrote:
> I was wondering about this but do we need screen_info for DUMMY_CONSOLE
> as well?
I thought so because my grep turned up a reference to screen_info in
dummycon.c but a closer look shows that only applies to arm.
--Mark
WARNING: multiple messages have this Message-ID (diff)
From: Mark Salter <msalter@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: add screen_info for console support
Date: Tue, 20 Aug 2013 14:04:04 -0400 [thread overview]
Message-ID: <1377021844.3591.1.camel@t520.redhat.com> (raw)
In-Reply-To: <20130820171453.GF21383@arm.com>
On Tue, 2013-08-20 at 18:14 +0100, Catalin Marinas wrote:
> I was wondering about this but do we need screen_info for DUMMY_CONSOLE
> as well?
I thought so because my grep turned up a reference to screen_info in
dummycon.c but a closer look shows that only applies to arm.
--Mark
next prev parent reply other threads:[~2013-08-20 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 16:22 [PATCH] arm64: add screen_info for console support Mark Salter
2013-08-18 16:22 ` Mark Salter
2013-08-20 13:37 ` Will Deacon
2013-08-20 13:37 ` Will Deacon
2013-08-20 17:14 ` Catalin Marinas
2013-08-20 17:14 ` Catalin Marinas
2013-08-20 18:04 ` Mark Salter [this message]
2013-08-20 18:04 ` Mark Salter
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=1377021844.3591.1.camel@t520.redhat.com \
--to=msalter@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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.