From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: stable <stable@vger.kernel.org>, Mark Zhang <markz@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Jinyoung Park <jinyoungp@nvidia.com>,
Venkat Reddy Talla <vreddytalla@nvidia.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] regmap-irq: do not write mask register if mask_base is zero
Date: Wed, 17 Jul 2019 16:54:17 +0900 [thread overview]
Message-ID: <20190717075417.GB13620@kroah.com> (raw)
In-Reply-To: <CACRpkdbcobeABjcA8+_cAjgddZnmHwoCx4pqAPbSS1GDNm6J2g@mail.gmail.com>
On Wed, Jul 17, 2019 at 09:42:00AM +0200, Linus Walleij wrote:
> Hi Greg,
>
> On Mon, May 20, 2019 at 7:23 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> > From: Mark Zhang <markz@nvidia.com>
> >
> > commit 7151449fe7fa5962c6153355f9779d6be99e8e97 upstream.
> >
> > If client have not provided the mask base register then do not
> > write into the mask register.
> >
> > Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> > Signed-off-by: Jinyoung Park <jinyoungp@nvidia.com>
> > Signed-off-by: Venkat Reddy Talla <vreddytalla@nvidia.com>
> > Signed-off-by: Mark Zhang <markz@nvidia.com>
> > Signed-off-by: Mark Brown <broonie@kernel.org>
> > ---
> > This commit was found in an nVidia product tree based on
> > v4.19, and looks like definitive stable material to me.
> > It should go into v4.19 only as far as I can tell.
>
> Was this missed or is there some reason for why this didn't get
> queued to stable?
I think it was missed, sorry :(
Now queued up.
greg k-h
next prev parent reply other threads:[~2019-07-17 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 17:21 [PATCH] regmap-irq: do not write mask register if mask_base is zero Linus Walleij
2019-07-17 7:42 ` Linus Walleij
2019-07-17 7:54 ` Greg Kroah-Hartman [this message]
2019-07-17 7:55 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2019-01-14 9:32 Mark Zhang
2019-01-14 9:32 ` Mark Zhang
2019-01-14 9:42 ` Mark Zhang
2019-01-14 9:42 ` Mark Zhang
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=20190717075417.GB13620@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=jinyoungp@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=markz@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=vreddytalla@nvidia.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.