All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Sasha Levin <sashal@kernel.org>, linux-i2c@vger.kernel.org
Cc: Wolfram Sang <wsa@the-dreams.de>,
	stable@vger.kernel.org,
	Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH] i2c: Prevent runtime suspend of adapter when Host Notify is required
Date: Thu, 2 May 2019 15:32:24 +0300	[thread overview]
Message-ID: <7f989564-e994-5be6-02da-2838639efe59@linux.intel.com> (raw)
In-Reply-To: <20190430155637.1B45E21743@mail.kernel.org>

On 4/30/19 6:56 PM, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: c5eb1190074c PCI / PM: Allow runtime PM without callback functions.
> 
> The bot has tested the following trees: v5.0.10, v4.19.37.
> 
> v5.0.10: Build OK!
> v4.19.37: Failed to apply! Possible dependencies:
>      6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")
>      93b6604c5a66 ("i2c: Allow recovery of the initial IRQ by an I2C client device.")
> 
> 
> How should we proceed with this patch?
> 
There's also dependency to commit
b9bb3fdf4e87 ("i2c: Remove unnecessary call to irq_find_mapping")

Without it 93b6604c5a66 doesn't apply.

Otherwise my patch don't have dependency into these so I can have 
another version for 4.19 if needed.

I got impression from the mail thread for 6f108dd70d30 that it could be 
also stable material but cannot really judge.

Charles: does your commits b9bb3fdf4e87 and 6f108dd70d30 with the fix 
93b6604c5a66 qualify for 4.19? (background: my fix doesn't apply without 
them but doesn't depend on them).

-- 
Jarkko

  parent reply	other threads:[~2019-05-02 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 14:23 [PATCH] i2c: Prevent runtime suspend of adapter when Host Notify is required Jarkko Nikula
2019-04-30 15:42 ` Rafael J. Wysocki
2019-05-02  8:07 ` Keijo Vaara
     [not found] ` <20190430155637.1B45E21743@mail.kernel.org>
2019-05-02 12:32   ` Jarkko Nikula [this message]
2019-05-02 15:32     ` Charles Keepax
2019-05-02 15:32       ` Charles Keepax
2019-05-05 12:54       ` Greg KH
2019-05-02 16:43 ` Wolfram Sang

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=7f989564-e994-5be6-02da-2838639efe59@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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.