Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220718163158.42176b4e@canb.auug.org.au> <YtXF8TUZHNRUUyJh@kroah.com>
 <CACeCKafbgLmhLoYQiTTDkeeJ26HqFYBHXtcpwQkzOyO9LESEFw@mail.gmail.com>
 <YtZUJr4oIIALgdO+@kroah.com> <YtadE201j+dt5jJx@kroah.com>
In-Reply-To: <YtadE201j+dt5jJx@kroah.com>
From:   Prashant Malani <pmalani@chromium.org>
Date:   Tue, 19 Jul 2022 10:11:44 -0700
Message-ID: <CACeCKae5aeK4wU_=+EXFnEHKsFbRnvxo14KtZgMAYw+zNpnKBg@mail.gmail.com>
Subject: Re: linux-next: build failure after merge of the usb tree
To:     Greg KH <greg@kroah.com>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Benson Leung <bleung@google.com>,
        Guenter Roeck <groeck@chromium.org>,
        Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        Tzung-Bi Shih <tzungbi@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Jul 19, 2022 at 5:30 AM Greg KH <greg@kroah.com> wrote:
> > > 3. Revert the entire cros-typec-switch (patches 3-9) series from
> > > usb-next and wait till after the merge window to apply it to
> > > chrome-platform directly.
> >
> > I think I'll just do #3 to resolve the issue.  I'll do it in a few
> > hours.
>
> Now all reverted from my tree.  Please send these changs through the
> platform tree after the next -rc1 is released so that you don't end up
> with build problems again.

Will do. Thank you for catching this and reverting the patches. Sorry
for the trouble.

BR,

-Prashant