From: Saul Wold <sgw@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] shadow-securetty: add freescale lpuart
Date: Thu, 24 Jul 2014 10:13:05 -0700 [thread overview]
Message-ID: <53D13EA1.4070707@linux.intel.com> (raw)
In-Reply-To: <53D11221.9070704@windriver.com>
On 07/24/2014 07:03 AM, Mark Hatle wrote:
> We should probably be setting up the securetty file in a machine
> specific way.
>
> Doing it generically just pollutes the file with more stuff a specific
> user won't want.
>
> (Note, you aren't the first to do this.. so right now it's probably the
> best answer, but we should fix this in the future.)
>
Mark,
can you please file a bug to track this, I will mark it as an unassigned
future / low for someone to pick up.
Sau!
> --Mark
>
> On 7/24/14, 2:44 AM, Stefan Agner wrote:
>> Add Freescale lpuart tty's (ttyLPx) to securetty. Freescale Vybrid
>> devices running upstream kernel use this driver.
>>
>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>> ---
>> meta/recipes-extended/shadow/files/securetty | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/meta/recipes-extended/shadow/files/securetty
>> b/meta/recipes-extended/shadow/files/securetty
>> index 0b1629f..d919993 100644
>> --- a/meta/recipes-extended/shadow/files/securetty
>> +++ b/meta/recipes-extended/shadow/files/securetty
>> @@ -137,6 +137,14 @@ ttymxc3
>> ttymxc4
>> ttymxc5
>>
>> +# Freescale lpuart ports
>> +ttyLP0
>> +ttyLP1
>> +ttyLP2
>> +ttyLP3
>> +ttyLP4
>> +ttyLP5
>> +
>> # Standard serial ports, with devfs
>> tts/0
>> tts/1
>>
>
prev parent reply other threads:[~2014-07-24 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 7:44 [PATCH] shadow-securetty: add freescale lpuart Stefan Agner
2014-07-24 14:03 ` Mark Hatle
2014-07-24 17:13 ` Saul Wold [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=53D13EA1.4070707@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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