linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	linux-tegra@vger.kernel.org, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] i2c: tegra: Remove suspend-resume
Date: Thu, 31 May 2018 01:17:33 +0300	[thread overview]
Message-ID: <cf08bb15-f547-5c23-c998-233a003eddf3@gmail.com> (raw)
In-Reply-To: <20180530202508.raee7klc2q3qoddo@ninjato>

On 30.05.2018 23:25, Wolfram Sang wrote:
> 
>> Applied to for-next, thanks!
> 
> I removed the stable tag, though. I am not 100% sure if there are not
> any side-effects for other users. If you still think it should go to
> stable, please mention this patch to stable@ after it was applied to
> linus tree. Maybe with a word or two about regression safety.
> 

Backporting to stable isn't really necessary, so no objections from me. Thank you.

  reply	other threads:[~2018-05-30 22:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 21:13 [PATCH v1] i2c: tegra: Remove suspend-resume Dmitry Osipenko
2018-05-14 11:59 ` Thierry Reding
2018-05-14 12:18   ` Wolfram Sang
2018-05-14 13:03     ` Dmitry Osipenko
2018-05-14 12:21   ` Laxman Dewangan
2018-05-14 12:47     ` Thierry Reding
2018-05-14 12:51     ` Dmitry Osipenko
2018-05-29 18:06       ` Wolfram Sang
2018-05-30 10:59         ` Laxman Dewangan
2018-05-30 20:18 ` Wolfram Sang
2018-05-30 20:25   ` Wolfram Sang
2018-05-30 22:17     ` Dmitry Osipenko [this message]
2018-10-17 13:59 ` Jon Hunter
2018-10-17 14:30   ` Dmitry Osipenko
2018-10-17 19:41     ` Jon Hunter
2018-10-17 20:49       ` Dmitry Osipenko

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=cf08bb15-f547-5c23-c998-233a003eddf3@gmail.com \
    --to=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).