From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Oct 29 (tty->raw)
Date: Mon, 29 Oct 2012 07:13:24 -0700 [thread overview]
Message-ID: <20121029141324.GA23983@kroah.com> (raw)
In-Reply-To: <508E0345.1010600@xenotime.net>
On Sun, Oct 28, 2012 at 09:17:09PM -0700, Randy Dunlap wrote:
> On 10/28/2012 08:46 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20121026:
> >
>
>
> Who made some changes that remove tty->raw ?
Jiri did.
> There is still one occurrence in arch/um that is causing
> a build error (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'
Known issue, it is being worked on.
thanks,
greg k-h
prev parent reply other threads:[~2012-10-29 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 3:46 linux-next: Tree for Oct 29 Stephen Rothwell
2012-10-29 4:17 ` linux-next: Tree for Oct 29 (tty->raw) Randy Dunlap
2012-10-29 14:13 ` Greg Kroah-Hartman [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=20121029141324.GA23983@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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).