linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evan Green <evgreen@chromium.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	Enric Balletbo Serra <eballetbo@gmail.com>,
	Ravi Chandra Sadineni <ravisadineni@chromium.org>,
	Rajat Jain <rajatja@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Benson Leung <bleung@chromium.org>,
	Tim Wawrzynczak <twawrzynczak@chromium.org>
Subject: Re: [PATCH v3] platform/chrome: Expose resume result via debugfs
Date: Fri, 12 Jul 2019 10:11:47 -0700	[thread overview]
Message-ID: <CAE=gft5yfO5-6bTcHE4HKs4FV=Z4E43xQLe9TWfSAcvpOREyXQ@mail.gmail.com> (raw)
In-Reply-To: <CAE=gft6e46pL4-4eC5LPUgePj4ibWzJPzKHJ3_oeFuwoM0K+QQ@mail.gmail.com>

On Fri, Jul 12, 2019 at 10:04 AM Evan Green <evgreen@chromium.org> wrote:
>
> On Mon, Jul 1, 2019 at 6:41 AM Enric Balletbo i Serra
> <enric.balletbo@collabora.com> wrote:
> >
> >
> >
> > On 1/7/19 8:01, Lee Jones wrote:
> > > On Thu, 27 Jun 2019, Enric Balletbo Serra wrote:
> > >
> > >> Hi Evan, Lee,
> > >>
> > >> Missatge de Evan Green <evgreen@chromium.org> del dia dj., 27 de juny
> > >> 2019 a les 22:46:
> > >>>
> > >>> For ECs that support it, the EC returns the number of slp_s0
> > >>> transitions and whether or not there was a timeout in the resume
> > >>> response. Expose the last resume result to usermode via debugfs so
> > >>> that usermode can detect and report S0ix timeouts.
> > >>>
> > >>> Signed-off-by: Evan Green <evgreen@chromium.org>
> > >>
> > >> Acked-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> > >>
> > >> Lee, actually this patch depends on some patches from chrome-platform
> > >> to apply cleanly. Once is fine with you and if you're happy to have
> > >> this merged for 5.3, I can just carry the patch with me, shouldn't be
> > >> any conflicts with your current changes or if you prefer I can create
> > >> an immutable branch for you.
> > >
> > > I won't be taking any more patches this cycle, so if you're sure that
> > > it does not conflict, there is no need for an immutable branch.
> > >
> > > Acked-by: Lee Jones <lee.jones@linaro.org>
> > >
> >
> > Thanks Lee.
> >
> > I think the patch is simple enough, I queued for the autobuilders to play with,
> > and if all goes well I'll add for 5.3 via chrome-platform.
> >
>
> I was hoping to pick this patch from a maintainer's tree, has it
> landed anywhere?
> -Evan

Nevermind, it's all the way in Linus' tree. Sorry for the spam, and
thanks Benson for the heads up!
-Evan

      reply	other threads:[~2019-07-12 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 20:44 [PATCH v3] platform/chrome: Expose resume result via debugfs Evan Green
2019-06-27 21:18 ` Enric Balletbo Serra
2019-07-01  6:01   ` Lee Jones
2019-07-01 13:41     ` Enric Balletbo i Serra
2019-07-12 17:04       ` Evan Green
2019-07-12 17:11         ` Evan Green [this message]

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='CAE=gft5yfO5-6bTcHE4HKs4FV=Z4E43xQLe9TWfSAcvpOREyXQ@mail.gmail.com' \
    --to=evgreen@chromium.org \
    --cc=bleung@chromium.org \
    --cc=eballetbo@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rajatja@chromium.org \
    --cc=ravisadineni@chromium.org \
    --cc=twawrzynczak@chromium.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 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).