From: Guenter Roeck <linux@roeck-us.net>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-cris-kernel@axis.com,
Jesper Nilsson <jesper.nilsson@axis.com>,
kernel@pengutronix.de
Subject: Re: [PATCH -next] serial: etraxfs-uart: Update gpiod API
Date: Wed, 22 Jul 2015 07:51:32 -0700 [thread overview]
Message-ID: <55AFADF4.5030409@roeck-us.net> (raw)
In-Reply-To: <20150722070659.GK9981@pengutronix.de>
On 07/22/2015 12:06 AM, Uwe Kleine-König wrote:
> While I stumbled over the calls to gpiod_get variants in the etraxfs
> serial driver I noticed several problems with that driver. I pointed
> them out in
>
> http://www.spinics.net/lists/linux-serial/msg17794.html
>
> . If you read the follow-ups Jesper Nilsson then said:
>
> I can push a patch that just drops all signal handling (since
> it's bogus ATM), or you can ignore the driver as currently
> implemented.
>
If you want to mark the driver as BROKEN due to those other problems,
go ahead, and I'll drop the architecture from my tests. But it should
not be marked BROKEN because you did not update an API.
> I explicitly did the latter. Apart from that single driver I fixed all
> users. @Jesper: You said you poked Niklas to care for that. Any news
> from that front?
>
> I'm all for the usual habit that API changes should be handled by the
> API changer. But if the code was already relying on undefined behaviour
> before the change and fixing that needs testing on the respective
> hardware, I think pushing the needed work back to the driver owner is
> fine. IMHO a simple build fix that doesn't fix the brokeness isn't that
> helpful here.
>
The driver works fine for me (in qemu), possibly because qemu doesn't
use/need modem lines.
Guenter
next prev parent reply other threads:[~2015-07-22 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 20:34 [PATCH -next] serial: etraxfs-uart: Update gpiod API Guenter Roeck
2015-07-21 21:01 ` Uwe Kleine-König
2015-07-21 22:17 ` Guenter Roeck
2015-07-22 7:06 ` Uwe Kleine-König
2015-07-22 14:51 ` Guenter Roeck [this message]
2015-07-22 15:31 ` Niklas Cassel
2015-07-23 22:23 ` Greg Kroah-Hartman
2015-07-24 6:33 ` Uwe Kleine-König
2015-07-27 13:16 ` Linus Walleij
2015-07-27 13:29 ` Niklas Cassel
2015-07-27 13:59 ` Uwe Kleine-König
2015-07-27 14:08 ` 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=55AFADF4.5030409@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=jesper.nilsson@axis.com \
--cc=jslaby@suse.com \
--cc=kernel@pengutronix.de \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).