From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Jonathan Kim <jonathankim@gctsemi.com>,
linux-kernel@vger.kernel.org, Dean ahn <deanahn@gctsemi.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 29 (staging/gdm724x)
Date: Mon, 29 Jul 2013 12:28:37 -0700 [thread overview]
Message-ID: <20130729192837.GB9191@kroah.com> (raw)
In-Reply-To: <51F6A0A9.5040702@infradead.org>
On Mon, Jul 29, 2013 at 10:04:41AM -0700, Randy Dunlap wrote:
> On 07/28/13 23:39, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20130726:
> >
>
> on i386:
> # CONFIG_TTY is not set
Thanks, now fixed.
greg k-h
prev parent reply other threads:[~2013-07-29 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 6:39 linux-next: Tree for Jul 29 Stephen Rothwell
2013-07-29 17:04 ` linux-next: Tree for Jul 29 (staging/gdm724x) Randy Dunlap
2013-07-29 19:28 ` 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=20130729192837.GB9191@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=deanahn@gctsemi.com \
--cc=devel@driverdev.osuosl.org \
--cc=jonathankim@gctsemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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).