All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Sasha Levin <sashal@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH STABLE v4.19.15] gpiolib: fix line event timestamps for nested irqs
Date: Wed, 16 Jan 2019 17:02:16 +0100	[thread overview]
Message-ID: <20190116160216.GA4594@kroah.com> (raw)
In-Reply-To: <20190116153557.13720-1-brgl@bgdev.pl>

On Wed, Jan 16, 2019 at 04:35:57PM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> 
> Nested interrupts run inside the calling thread's context and the top
> half handler is never called which means that we never read the
> timestamp.
> 
> This issue came up when trying to read line events from a gpiochip
> using regmap_irq_chip for interrupts.
> 
> Fix it by reading the timestamp from the irq thread function if it's
> still 0 by the time the second handler is called.
> 
> Fixes: d58f2bf261fd ("gpio: Timestamp events in hardirq handler")
> Cc: stable@vger.kernel.org
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
> Hi Sasha,
> 
> this is a backport for v4.19.y series. The original patch didn't apply
> due to a conflict.

What is the git commit id for this patch in Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2019-01-16 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 15:35 [PATCH STABLE v4.19.15] gpiolib: fix line event timestamps for nested irqs Bartosz Golaszewski
2019-01-16 16:02 ` Greg KH [this message]
2019-01-16 16:18   ` Bartosz Golaszewski

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=20190116160216.GA4594@kroah.com \
    --to=greg@kroah.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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.