From: Greg Kroah-Hartman <greg@kroah.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: Dann Frazier <dann.frazier@canonical.com>,
Manoj Iyer <manoj.iyer@canonical.com>,
linux-serial@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Christopher Covington <cov@mykolab.com>
Subject: Re: [PATCH] [v2][for 4.11]tty: acpi/spcr: QDF2400 E44 checks for wrong OEM revision
Date: Wed, 22 Mar 2017 16:45:26 +0100 [thread overview]
Message-ID: <20170322154526.GA17123@kroah.com> (raw)
In-Reply-To: <CAOZdJXW6k=fwaD96dPSikK6kntbKFuhypALG8YGbcWcBcRcLiw@mail.gmail.com>
On Wed, Mar 22, 2017 at 10:13:00AM -0500, Timur Tabi wrote:
> On Sun, Mar 12, 2017 at 11:19 PM, Timur Tabi <timur@codeaurora.org> wrote:
> > On Tue, Feb 28, 2017 at 2:30 PM, Timur Tabi <timur@codeaurora.org> wrote:
> >> For Qualcomm Technologies QDF2400 SOCs that are affected by erratum E44,
> >> the ACPI oem_revision field is actually set to 1, not 0.
> >>
> >> Fixes: d8a4995bcea1 ("tty: pl011: Work around QDF2400 E44 stuck BUSY bit")
> >>
> >> Tested-by: Manoj Iyer <manoj.iyer@canonical.com>
> >> Signed-off-by: Timur Tabi <timur@codeaurora.org>
> >
> > Greg, this is a critical fix for our platform. Can you please pick it
> > up for 4.11-rc3? Thank you.
>
> Ok, how about 4.11-rc4?
It's in the queue in tty-linus, right? If so, that should make it into
4.11-final.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [v2][for 4.11]tty: acpi/spcr: QDF2400 E44 checks for wrong OEM revision
Date: Wed, 22 Mar 2017 16:45:26 +0100 [thread overview]
Message-ID: <20170322154526.GA17123@kroah.com> (raw)
In-Reply-To: <CAOZdJXW6k=fwaD96dPSikK6kntbKFuhypALG8YGbcWcBcRcLiw@mail.gmail.com>
On Wed, Mar 22, 2017 at 10:13:00AM -0500, Timur Tabi wrote:
> On Sun, Mar 12, 2017 at 11:19 PM, Timur Tabi <timur@codeaurora.org> wrote:
> > On Tue, Feb 28, 2017 at 2:30 PM, Timur Tabi <timur@codeaurora.org> wrote:
> >> For Qualcomm Technologies QDF2400 SOCs that are affected by erratum E44,
> >> the ACPI oem_revision field is actually set to 1, not 0.
> >>
> >> Fixes: d8a4995bcea1 ("tty: pl011: Work around QDF2400 E44 stuck BUSY bit")
> >>
> >> Tested-by: Manoj Iyer <manoj.iyer@canonical.com>
> >> Signed-off-by: Timur Tabi <timur@codeaurora.org>
> >
> > Greg, this is a critical fix for our platform. Can you please pick it
> > up for 4.11-rc3? Thank you.
>
> Ok, how about 4.11-rc4?
It's in the queue in tty-linus, right? If so, that should make it into
4.11-final.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-22 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 20:30 [PATCH] [v2][for 4.11]tty: acpi/spcr: QDF2400 E44 checks for wrong OEM revision Timur Tabi
2017-02-28 20:30 ` Timur Tabi
2017-03-13 4:19 ` Timur Tabi
2017-03-13 4:19 ` Timur Tabi
2017-03-22 15:13 ` Timur Tabi
2017-03-22 15:13 ` Timur Tabi
2017-03-22 15:45 ` Greg Kroah-Hartman [this message]
2017-03-22 15:45 ` Greg Kroah-Hartman
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=20170322154526.GA17123@kroah.com \
--to=greg@kroah.com \
--cc=cov@mykolab.com \
--cc=dann.frazier@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=manoj.iyer@canonical.com \
--cc=timur@codeaurora.org \
/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.