From: "Yang, Hyungwoo" <hyungwoo.yang@intel.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kadam, Rushikesh S" <rushikesh.s.kadam@intel.com>,
"jettrink@chromium.org" <jettrink@chromium.org>
Subject: RE: [PATCH] platform/chrome: fix crash during suspend
Date: Tue, 4 Jun 2019 16:17:38 +0000 [thread overview]
Message-ID: <7A4F467111FEF64486F40DFE7DF3500A221AFDEC@ORSMSX121.amr.corp.intel.com> (raw)
In-Reply-To: <2fc73fbf-8d30-9aba-c12e-799e6f2a824f@collabora.com>
> -----Original Message-----
> From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> Sent: Tuesday, June 4, 2019 8:04 AM
> To: Yang, Hyungwoo <hyungwoo.yang@intel.com>
> Cc: linux-kernel@vger.kernel.org; Kadam, Rushikesh S <rushikesh.s.kadam@intel.com>; jettrink@chromium.org
> Subject: Re: [PATCH] platform/chrome: fix crash during suspend
> >>>
> >>
> >> As this patch is a fix for '26a14267aff2 platform/chrome: Add ChromeOS EC ISHTP driver' which is still for-next material, do you mind if I squash both patches?
> >>
> >> If you don't mind I'll add your Signed-off and a small comment saying that you fixed this.
> >
> > I don't mind. please do whatever you want. but it has dependency with
> > https://patchwork.kernel.org/project/linux-input/list/?series=124780
>
> What patches exactly? The link points me to a big list of patches. And do you mean that this patch is a fix for a patch that didn't land yet and current code is not wrong?
I'm sorry I didn't know I made mistake with "send-mail". I've submitted new one(v4) as they asked me.
https://patchwork.kernel.org/project/linux-input/list/?series=126697
Thanks,
Hyungwoo
next prev parent reply other threads:[~2019-06-04 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 4:03 [PATCH] platform/chrome: fix crash during suspend Hyungwoo Yang
2019-05-31 10:21 ` Enric Balletbo i Serra
2019-05-31 18:15 ` Yang, Hyungwoo
2019-06-04 15:03 ` Enric Balletbo i Serra
2019-06-04 16:17 ` Yang, Hyungwoo [this message]
2019-07-29 11:29 ` Enric Balletbo i Serra
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=7A4F467111FEF64486F40DFE7DF3500A221AFDEC@ORSMSX121.amr.corp.intel.com \
--to=hyungwoo.yang@intel.com \
--cc=enric.balletbo@collabora.com \
--cc=jettrink@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rushikesh.s.kadam@intel.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 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).