From: Jiri Slaby <jslaby@suse.cz>
To: gregkh@linuxfoundation.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
"Uwe Kleine-König" <kernel@pengutronix.de>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Peter Korsgaard" <jacmet@sunsite.dk>,
"Michal Simek" <michal.simek@xilinx.com>,
"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
linux-arm-kernel@lists.infradead.org,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>
Subject: Re: [PATCH] tty: serial, return values platform_get_irq, part II.
Date: Fri, 29 Apr 2016 11:24:44 +0200 [thread overview]
Message-ID: <5723285C.3080008@suse.cz> (raw)
In-Reply-To: <1461921721-30169-1-git-send-email-jslaby@suse.cz>
On 04/29/2016, 11:22 AM, Jiri Slaby wrote:
> When commit "TTY: serial, handle platform_get_irq retval properly" was
> merged, it was pointed out, that platform_get_irq is more peculiar
> than it seems.
>
> platform_get_irq can actually return zero for some platforms. So
> reverts parts of the aforementioned commits which did the worng thing
> on those platforms.
Given I double checked the code, I should do so for the commit message
too. Please scratch this one due to the commit message.
thanks,
--
js
suse labs
WARNING: multiple messages have this Message-ID (diff)
From: jslaby@suse.cz (Jiri Slaby)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] tty: serial, return values platform_get_irq, part II.
Date: Fri, 29 Apr 2016 11:24:44 +0200 [thread overview]
Message-ID: <5723285C.3080008@suse.cz> (raw)
In-Reply-To: <1461921721-30169-1-git-send-email-jslaby@suse.cz>
On 04/29/2016, 11:22 AM, Jiri Slaby wrote:
> When commit "TTY: serial, handle platform_get_irq retval properly" was
> merged, it was pointed out, that platform_get_irq is more peculiar
> than it seems.
>
> platform_get_irq can actually return zero for some platforms. So
> reverts parts of the aforementioned commits which did the worng thing
> on those platforms.
Given I double checked the code, I should do so for the commit message
too. Please scratch this one due to the commit message.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2016-04-29 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 9:22 [PATCH] tty: serial, return values platform_get_irq, part II Jiri Slaby
2016-04-29 9:22 ` Jiri Slaby
2016-04-29 9:24 ` Jiri Slaby [this message]
2016-04-29 9:24 ` Jiri Slaby
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=5723285C.3080008@suse.cz \
--to=jslaby@suse.cz \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=jacmet@sunsite.dk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=michal.simek@xilinx.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=soren.brinkmann@xilinx.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.