From: James Hogan <james.hogan@mips.com>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: linux-mips@linux-mips.org, linux-serial@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Nicolas Schichan <nschichan@freebox.fr>
Subject: Re: [PATCH 0/3] MIPS: AR7: assorted fixes
Date: Wed, 8 Nov 2017 22:03:22 +0000 [thread overview]
Message-ID: <20171108220322.GO15260@jhogan-linux> (raw)
In-Reply-To: <20171029152721.6770-1-jonas.gorski@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
On Sun, Oct 29, 2017 at 04:27:18PM +0100, Jonas Gorski wrote:
> This patchset fixes a few issues found in AR7 that accumulated in the
> past few years. One was fixed for ages in OpenWrt/LEDE and never made
> it upstream, the others weren't noticed until now.
>
> Jonas Gorski (2):
> MIPS: AR7: defer registration of GPIO
> MIPS: AR7: ensure the port type's FCR value is used
>
> Oswald Buddenhagen (1):
> MIPS: AR7: ensure that serial ports are properly set up
Thanks. Patches 1 + 2 applied for 4.14.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-11-08 22:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 15:27 [PATCH 0/3] MIPS: AR7: assorted fixes Jonas Gorski
2017-10-29 15:27 ` [PATCH 1/3] MIPS: AR7: defer registration of GPIO Jonas Gorski
2017-10-29 17:33 ` Florian Fainelli
2017-10-29 15:27 ` [PATCH 2/3] MIPS: AR7: ensure that serial ports are properly set up Jonas Gorski
2017-10-29 17:33 ` Florian Fainelli
2017-10-29 15:27 ` [PATCH RFC 3/3] MIPS: AR7: ensure the port type's FCR value is used Jonas Gorski
2017-11-14 11:02 ` James Hogan
2017-12-28 15:38 ` Jonas Gorski
2018-01-02 8:40 ` James Hogan
2018-01-22 13:07 ` James Hogan
2018-01-22 13:34 ` Greg Kroah-Hartman
2017-11-08 22:03 ` James Hogan [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=20171108220322.GO15260@jhogan-linux \
--to=james.hogan@mips.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=nschichan@freebox.fr \
--cc=ralf@linux-mips.org \
--cc=yoshihiro.yunomae.ez@hitachi.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 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).