From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Liang Li <liang.li@windriver.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
<linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-serial@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: linux-next: Tree for Jan 23 (pch_uart.c)
Date: Thu, 24 Jan 2013 15:15:37 +1100 [thread overview]
Message-ID: <20130124151537.12c139821173713bf858fa40@canb.auug.org.au> (raw)
In-Reply-To: <20130124023054.GA21851@localhost>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
Hi,
On Thu, 24 Jan 2013 10:30:54 +0800 Liang Li <liang.li@windriver.com> wrote:
>
> Should I add a fix for the compile error .. or do squash then send out
> refreshed patch ?
You need to send a fix patch to Greg based on his tty tree
(git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-24 4:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 6:43 linux-next: Tree for Jan 23 Stephen Rothwell
2013-01-23 22:18 ` Stephen Rothwell
2013-01-23 23:10 ` linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c]) Randy Dunlap
2013-01-23 23:23 ` Herbert Xu
2013-01-23 23:41 ` Randy Dunlap
2013-01-26 10:02 ` Jonathan Cameron
2013-01-23 23:28 ` linux-next: Tree for Jan 23 (pch_uart.c) Randy Dunlap
2013-01-24 2:06 ` Stephen Rothwell
2013-01-24 2:30 ` Liang Li
2013-01-24 4:15 ` Stephen Rothwell [this message]
2013-01-24 4:25 ` Liang Li
2013-01-23 23:56 ` linux-next: Tree for Jan 23 (hvc and virtio_console) 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=20130124151537.12c139821173713bf858fa40@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=liang.li@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).