From: Timur Tabi <timur@codeaurora.org>
To: Christopher Covington <cov@codeaurora.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Peter Hurley <peter@hurleysoftware.com>,
Aleksey Makarov <aleksey.makarov@linaro.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, shankerd@codeaurora.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Russell King <linux@armlinux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-acpi@vger.kernel.org, linux-serial@vger.kernel.org,
Mark Langsdorf <mlangsdo@redhat.com>,
Mark Salter <msalter@redhat.com>, Jon Masters <jcm@redh>
Subject: Re: [PATCH v2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit
Date: Wed, 15 Feb 2017 08:05:34 -0600 [thread overview]
Message-ID: <2d3173f5-8818-21cd-eccd-10fc6d5ec3bd@codeaurora.org> (raw)
In-Reply-To: <09772d07b3d6782690728ea171ac6e9e@codeaurora.org>
Christopher Covington wrote:
> Nothing needs QDF2400 erratum 44. Software should try to detect the presence
> of the erratum. So I think qdf2400_e44_detected or qdf2400_e44_present would
> make sense. But those suffixes don't add substantial value in my opinion.
I'd be okay with qdf2400_e44_detected or qdf2400_e44_present. I think it's a
lot clearer. Another idea is "has_qdf2400_e44".
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
WARNING: multiple messages have this Message-ID (diff)
From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit
Date: Wed, 15 Feb 2017 08:05:34 -0600 [thread overview]
Message-ID: <2d3173f5-8818-21cd-eccd-10fc6d5ec3bd@codeaurora.org> (raw)
In-Reply-To: <09772d07b3d6782690728ea171ac6e9e@codeaurora.org>
Christopher Covington wrote:
> Nothing needs QDF2400 erratum 44. Software should try to detect the presence
> of the erratum. So I think qdf2400_e44_detected or qdf2400_e44_present would
> make sense. But those suffixes don't add substantial value in my opinion.
I'd be okay with qdf2400_e44_detected or qdf2400_e44_present. I think it's a
lot clearer. Another idea is "has_qdf2400_e44".
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@codeaurora.org>
To: Christopher Covington <cov@codeaurora.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Peter Hurley <peter@hurleysoftware.com>,
Aleksey Makarov <aleksey.makarov@linaro.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, shankerd@codeaurora.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Russell King <linux@armlinux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-acpi@vger.kernel.org, linux-serial@vger.kernel.org,
Mark Langsdorf <mlangsdo@redhat.com>,
Mark Salter <msalter@redhat.com>, Jon Masters <jcm@redhat.com>,
Neil Leeder <nleeder@codeaurora.org>
Subject: Re: [PATCH v2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit
Date: Wed, 15 Feb 2017 08:05:34 -0600 [thread overview]
Message-ID: <2d3173f5-8818-21cd-eccd-10fc6d5ec3bd@codeaurora.org> (raw)
In-Reply-To: <09772d07b3d6782690728ea171ac6e9e@codeaurora.org>
Christopher Covington wrote:
> Nothing needs QDF2400 erratum 44. Software should try to detect the presence
> of the erratum. So I think qdf2400_e44_detected or qdf2400_e44_present would
> make sense. But those suffixes don't add substantial value in my opinion.
I'd be okay with qdf2400_e44_detected or qdf2400_e44_present. I think it's a
lot clearer. Another idea is "has_qdf2400_e44".
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
next prev parent reply other threads:[~2017-02-15 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 23:53 [PATCH v2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Christopher Covington
2017-02-14 23:53 ` Christopher Covington
2017-02-15 2:39 ` Timur Tabi
2017-02-15 2:39 ` Timur Tabi
2017-02-15 12:24 ` Mark Rutland
2017-02-15 12:24 ` Mark Rutland
2017-02-15 12:24 ` Mark Rutland
2017-02-15 13:59 ` Christopher Covington
2017-02-15 13:59 ` Christopher Covington
2017-02-15 13:59 ` Christopher Covington
2017-02-15 14:05 ` Timur Tabi [this message]
2017-02-15 14:05 ` Timur Tabi
2017-02-15 14:05 ` Timur Tabi
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=2d3173f5-8818-21cd-eccd-10fc6d5ec3bd@codeaurora.org \
--to=timur@codeaurora.org \
--cc=aleksey.makarov@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=cov@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=jcm@redh \
--cc=jslaby@suse.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mlangsdo@redhat.com \
--cc=msalter@redhat.com \
--cc=peter@hurleysoftware.com \
--cc=rjw@rjwysocki.net \
--cc=robin.murphy@arm.com \
--cc=shankerd@codeaurora.org \
--cc=will.deacon@arm.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.