Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210203021539.745239-1-pmalani@chromium.org> <161242303435.1051580.1469403981857153644.b4-ty@chromium.org>
In-Reply-To: <161242303435.1051580.1469403981857153644.b4-ty@chromium.org>
From:   Prashant Malani <pmalani@chromium.org>
Date:   Thu, 4 Feb 2021 01:16:33 -0800
Message-ID: <CACeCKaekU7o57ucFM7RSNM0_0N8GLMc54Dp4VQYAxMnVaEnmNw@mail.gmail.com>
Subject: Re: [PATCH v2 1/2] platform/chrome: cros_ec: Import Type C control command
To:     Benson Leung <bleung@google.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Pi-Hsun Shih <pihsun@chromium.org>,
        "Gustavo A. R. Silva" <gustavoars@kernel.org>,
        Utkarsh Patel <utkarsh.h.patel@intel.com>,
        Enric Balletbo i Serra <enric.balletbo@collabora.com>,
        Guenter Roeck <groeck@chromium.org>,
        Mark Brown <broonie@kernel.org>,
        Benson Leung <bleung@chromium.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Thanks Benson,

On Wed, Feb 3, 2021 at 11:18 PM Benson Leung <bleung@google.com> wrote:
>
> Hi Prashant,
>
> On Tue, 2 Feb 2021 18:15:37 -0800, Prashant Malani wrote:
> > This command is used to communicate with the Chrome Embedded Controller
> > (EC) regarding USB Type C events and state.
> >
> > These header updates are included in the latest Chrome OS EC headers [1]
> >
> > [1]
> > https://chromium.googlesource.com/chromiumos/platform/ec/+/refs/heads/main/include/ec_commands.h
>
> Applied, thanks!
>
> [1/2] platform/chrome: cros_ec: Import Type C control command
>       commit: 3ec28d3673362076444e290bdb0d94ec6432dc09
> [2/2] platform/chrome: cros_ec_typec: Clear Type C disc events
>       commit: d521119c8b0d70b91971d632430ec1143e5d2e26

This (patch 2/2) now looks like it will lead to a conflict with the
following patch which went into Greg's usb tree:
cefc011f8daf ("platform/chrome: cros_ec_typec: Set Partner PD revision
from status")

If we want to submit stuff to for-next, perhaps the immutable branch
should be merged into for-next?