From: Jason Uy <jason.uy@broadcom.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Noam Camus <noamc@ezchip.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Wang Hongcheng <annie.wang@amd.com>,
Jason Uy <jason.uy@broadcom.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH v2 0/1] Allow hardware flow control to be used
Date: Wed, 11 Jan 2017 11:48:19 -0800 [thread overview]
Message-ID: <1484164100-9805-1-git-send-email-jason.uy@broadcom.com> (raw)
<clip: as before>
Changes from v1:
- Rebased to v4.10-rc4
- repo: https://github.com/torvalds/linux.git
Regards,
Jason
--
1.9.1
next reply other threads:[~2017-01-11 19:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 19:48 Jason Uy [this message]
2017-01-11 19:48 ` [PATCH v2 1/1] serial: 8250_dw: Allow hardware flow control to be used Jason Uy
2017-01-11 19:53 ` Andy Shevchenko
2017-01-13 1:33 ` Kefeng Wang
2017-01-13 1:33 ` Kefeng Wang
[not found] ` <CAAG0J9-n0toSJL8Ze8Esq81dYnpfrTd42bMiR94zw_btBLjsww@mail.gmail.com>
2017-03-01 18:50 ` Andy Shevchenko
2017-03-03 0:21 ` James Hogan
2017-03-03 0:21 ` James Hogan
2017-03-03 13:31 ` Andy Shevchenko
2017-03-03 17:33 ` Ray Jui
2017-03-03 17:43 ` Jason Uy
2017-03-03 23:07 ` James Hogan
2017-03-03 23:07 ` James Hogan
2017-03-04 0:02 ` Jason Uy
2017-03-04 0:11 ` James Hogan
2017-03-04 0:11 ` James Hogan
2017-03-03 23:23 ` James Hogan
2017-03-03 23:23 ` James Hogan
2017-03-04 2:56 ` Andy Shevchenko
2017-03-04 13:09 ` [PATCH] serial: 8250_dw: Fix breakage when HAVE_CLK=n James Hogan
2017-03-04 13:09 ` James Hogan
2017-03-04 14:37 ` Andy Shevchenko
2017-03-06 10:16 ` James Hogan
2017-03-06 10:16 ` James Hogan
2017-03-06 23:38 ` Jason Uy
2017-03-05 0:44 ` Heiko Stuebner
2017-03-13 11:14 ` James Hogan
2017-03-13 11:14 ` James Hogan
2017-03-14 2:21 ` Greg Kroah-Hartman
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=1484164100-9805-1-git-send-email-jason.uy@broadcom.com \
--to=jason.uy@broadcom.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=annie.wang@amd.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=noamc@ezchip.com \
--cc=wangkefeng.wang@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.