From: Jiri Slaby <jslaby@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Richard Weinberger <richard@nod.at>,
linux-next@vger.kernel.org, Alan Cox <alan@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
user-mode-linux-devel@lists.sourceforge.net,
Jiri Slaby <jirislaby@gmail.com>
Subject: Re: mmotm 2012-10-24-17-15 uploaded (uml)
Date: Sat, 27 Oct 2012 14:13:03 +0200 [thread overview]
Message-ID: <508BCFCF.70101@suse.cz> (raw)
In-Reply-To: <20121025134850.76cdb390565dfe5117bdef7e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On 10/25/2012 04:48 AM, Stephen Rothwell wrote:
> Hi Randy,
>
> On Wed, 24 Oct 2012 18:17:59 -0700 Randy Dunlap <rdunlap@xenotime.net> wrote:
>>
>> uml on x86_64 defconfig:
>>
>> arch/um/drivers/chan_kern.c: In function 'tty_receive_char':
>> arch/um/drivers/chan_kern.c:89:42: error: 'struct tty_struct' has no member named 'raw'
Hmm, that code looks doing weird stuff. This patch should fix it. But
I'm not sure why it was there at all, as n_tty should take care of the
raw case perfectly right away. I cannot find any clues in the git log as
to why it was added at all. It's there like since ever.
Could anybody with working UML (I'm unable to run UML ATM, it crashes
heavily during the bootup -- after terminals are shown) check whether
the patch actually works?
thanks,
--
js
suse labs
[-- Attachment #2: 0001-UM.patch --]
[-- Type: text/x-patch, Size: 1019 bytes --]
>From 3f60aa996467bf4a1bd4e62f80cb714ea6569fde Mon Sep 17 00:00:00 2001
From: Jiri Slaby <jslaby@suse.cz>
Date: Thu, 25 Oct 2012 16:40:59 +0200
Subject: [PATCH] UM:
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
---
arch/um/drivers/chan_kern.c | 17 ++---------------
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/arch/um/drivers/chan_kern.c b/arch/um/drivers/chan_kern.c
index c3bba73..e9a0abc 100644
--- a/arch/um/drivers/chan_kern.c
+++ b/arch/um/drivers/chan_kern.c
@@ -83,21 +83,8 @@ static const struct chan_ops not_configged_ops = {
static void tty_receive_char(struct tty_struct *tty, char ch)
{
- if (tty == NULL)
- return;
-
- if (I_IXON(tty) && !I_IXOFF(tty) && !tty->raw) {
- if (ch == STOP_CHAR(tty)) {
- stop_tty(tty);
- return;
- }
- else if (ch == START_CHAR(tty)) {
- start_tty(tty);
- return;
- }
- }
-
- tty_insert_flip_char(tty, ch, TTY_NORMAL);
+ if (tty)
+ tty_insert_flip_char(tty, ch, TTY_NORMAL);
}
static int open_one_chan(struct chan *chan)
--
1.7.12.4
next prev parent reply other threads:[~2012-10-27 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 0:16 mmotm 2012-10-24-17-15 uploaded akpm
2012-10-25 1:17 ` mmotm 2012-10-24-17-15 uploaded (uml) Randy Dunlap
2012-10-25 2:48 ` Stephen Rothwell
2012-10-27 12:13 ` Jiri Slaby [this message]
2012-10-25 3:42 ` mmotm 2012-10-24-17-15 uploaded Stephen Rothwell
2012-10-25 16:02 ` mmotm 2012-10-24-17-15 uploaded (drm/i915) Randy Dunlap
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=508BCFCF.70101@suse.cz \
--to=jslaby@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).