From: Linus Walleij <linus.walleij@linaro.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Sascha Weisenberger <sascha.weisenberger@siemens.com>
Subject: Re: [PATCH v6 00/10] serial/gpio: exar: Fixes and support for IOT2000
Date: Tue, 20 Jun 2017 13:38:28 +0200 [thread overview]
Message-ID: <CACRpkdbNPnNbk_r0NWEs4e7PuKmMf9KTjeRPRnxTOHuK-+ki2Q@mail.gmail.com> (raw)
In-Reply-To: <9520074b-3731-7bbe-d59d-cbed90ac16bb@siemens.com>
On Tue, Jun 20, 2017 at 10:54 AM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> On 2017-06-20 10:19, Linus Walleij wrote:
>> On Fri, Jun 9, 2017 at 8:33 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>
>>> This makes the gpio-exar driver usable, which was prevented by a number
>>> of fatal bugs, and adds support for the SIMATIC IOT2040 to the 8250-exar
>>> driver and, indirectly, to gpio-exar as well. It's a cross-subsystem
>>> series, so I'm also cross-posting to the serial and gpio lists.
>>>
>>> Changes in v6:
>>
>> I merged some of the patches, that applied. Let's see if they survive
>> in linux-next, else I guess we need to fix this in the -rcs or for the next
>> kernel cycle.
>
> Weird that things did not apply. I just did a cherry-pick for all those
> 10 patches on top of 5c996b7eb52c, and that went smoothly. Please let me
> know which baseline is needed, and I will rebase.
This was on the "devel" branch of my GPIO tree:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/log/?h=devel
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-06-20 11:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 18:33 [PATCH v6 00/10] serial/gpio: exar: Fixes and support for IOT2000 Jan Kiszka
2017-06-09 18:33 ` [PATCH v6 01/10] gpio-exar/8250-exar: Do not even instantiate a GPIO device for Commtech cards Jan Kiszka
2017-06-29 14:48 ` Greg Kroah-Hartman
2017-06-09 18:33 ` [PATCH v6 02/10] gpio-exar/8250-exar: Fix passing in of parent PCI device Jan Kiszka
2017-06-20 8:13 ` Linus Walleij
2017-06-09 18:33 ` [PATCH v6 03/10] gpio: exar: Allocate resources on behalf of the platform device Jan Kiszka
2017-06-20 8:14 ` Linus Walleij
2017-06-09 18:33 ` [PATCH v6 04/10] gpio: exar: Fix iomap request Jan Kiszka
2017-06-20 8:15 ` Linus Walleij
2017-06-09 18:33 ` [PATCH v6 05/10] gpio: exar: Fix reading of directions and values Jan Kiszka
2017-06-20 8:16 ` Linus Walleij
2017-06-09 18:33 ` [PATCH v6 06/10] gpio-exar/8250-exar: Rearrange gpiochip parenthood Jan Kiszka
2017-06-09 18:33 ` [PATCH v6 07/10] serial: exar: Factor out platform hooks Jan Kiszka
2017-06-29 14:48 ` Greg Kroah-Hartman
2017-06-09 18:33 ` [PATCH v6 08/10] platform: Accept const properties Jan Kiszka
2017-06-09 18:33 ` [PATCH v6 09/10] gpio-exar/8250-exar: Make set of exported GPIOs configurable Jan Kiszka
2017-06-09 18:33 ` [PATCH v6 10/10] serial: exar: Add support for IOT2040 device Jan Kiszka
2017-06-29 14:49 ` Greg Kroah-Hartman
2017-06-20 8:19 ` [PATCH v6 00/10] serial/gpio: exar: Fixes and support for IOT2000 Linus Walleij
2017-06-20 8:54 ` Jan Kiszka
2017-06-20 11:38 ` Linus Walleij [this message]
2017-06-21 6:29 ` Jan Kiszka
2017-06-23 20:09 ` Jan Kiszka
2017-06-29 9:51 ` Linus Walleij
2017-06-29 11:43 ` Andy Shevchenko
2017-06-29 14:49 ` Greg Kroah-Hartman
2017-06-29 22:13 ` Linus Walleij
2017-07-03 7:21 ` [PULL] " Jan Kiszka
2017-07-03 8:10 ` Linus Walleij
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=CACRpkdbNPnNbk_r0NWEs4e7PuKmMf9KTjeRPRnxTOHuK-+ki2Q@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sascha.weisenberger@siemens.com \
--cc=sudip.mukherjee@codethink.co.uk \
/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).