From: Timur Tabi <timur@freescale.com>
To: kumar.gala@freescale.com, benh@kernel.crashing.org,
greg@kroah.com, akpm@kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-console@vger.kerne
Subject: Re: [PATCH 6/7] [v2] tty/powerpc: introduce the ePAPR embedded hypervisor byte channel driver
Date: Wed, 22 Jun 2011 10:23:32 -0500 [thread overview]
Message-ID: <4E0208F4.4030800@freescale.com> (raw)
In-Reply-To: <1305830092-20104-1-git-send-email-timur@freescale.com>
Timur Tabi wrote:
> The ePAPR embedded hypervisor specification provides an API for "byte
> channels", which are serial-like virtual devices for sending and receiving
> streams of bytes. This driver provides Linux kernel support for byte
> channels via three distinct interfaces:
>
> 1) An early-console (udbg) driver. This provides early console output
> through a byte channel. The byte channel handle must be specified in a
> Kconfig option.
>
> 2) A normal console driver. Output is sent to the byte channel designated
> for stdout in the device tree. The console driver is for handling kernel
> printk calls.
>
> 3) A tty driver, which is used to handle user-space input and output. The
> byte channel used for the console is designated as the default tty.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
I know you guys are busy, but can I get an ACK or two on this patch, if there
are no issues with it? It's the only one of the seven that doesn't have one. I
think v2 has addressed all of the concerns raised on version 1.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: <kumar.gala@freescale.com>, <benh@kernel.crashing.org>,
<greg@kroah.com>, <akpm@kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<linux-console@vger.kernel.org>, <alan@lxorguk.ukuu.org.uk>,
<arnd@arndb.de>
Subject: Re: [PATCH 6/7] [v2] tty/powerpc: introduce the ePAPR embedded hypervisor byte channel driver
Date: Wed, 22 Jun 2011 10:23:32 -0500 [thread overview]
Message-ID: <4E0208F4.4030800@freescale.com> (raw)
In-Reply-To: <1305830092-20104-1-git-send-email-timur@freescale.com>
Timur Tabi wrote:
> The ePAPR embedded hypervisor specification provides an API for "byte
> channels", which are serial-like virtual devices for sending and receiving
> streams of bytes. This driver provides Linux kernel support for byte
> channels via three distinct interfaces:
>
> 1) An early-console (udbg) driver. This provides early console output
> through a byte channel. The byte channel handle must be specified in a
> Kconfig option.
>
> 2) A normal console driver. Output is sent to the byte channel designated
> for stdout in the device tree. The console driver is for handling kernel
> printk calls.
>
> 3) A tty driver, which is used to handle user-space input and output. The
> byte channel used for the console is designated as the default tty.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
I know you guys are busy, but can I get an ACK or two on this patch, if there
are no issues with it? It's the only one of the seven that doesn't have one. I
think v2 has addressed all of the concerns raised on version 1.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-06-22 15:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 18:34 [PATCH 6/7] [v2] tty/powerpc: introduce the ePAPR embedded hypervisor byte channel driver Timur Tabi
2011-06-22 15:23 ` Timur Tabi [this message]
2011-06-22 15:23 ` Timur Tabi
2011-07-03 1:43 ` Tabi Timur-B04825
2011-07-03 1:43 ` Tabi Timur-B04825
2011-07-03 1:43 ` Tabi Timur-B04825
2011-07-08 22:06 ` Greg KH
2011-07-08 22:06 ` Greg KH
2011-07-08 22:12 ` Timur Tabi
2011-07-08 22:12 ` Timur Tabi
2011-07-08 22:12 ` Timur Tabi
2011-07-08 22:15 ` Timur Tabi
2011-07-08 22:15 ` Timur Tabi
2011-07-08 22:15 ` Timur Tabi
2011-07-08 22:29 ` Greg KH
2011-07-08 22:29 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2011-05-19 18:34 [PATCH 6/7] [v2] " Timur Tabi
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=4E0208F4.4030800@freescale.com \
--to=timur@freescale.com \
--cc=akpm@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=kumar.gala@freescale.com \
--cc=linux-console@vger.kerne \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.