From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Rob Herring <robh@kernel.org>
Cc: Peter Chen <peter.chen@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux USB List <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>
Subject: Re: ChipIdea USB regression
Date: Tue, 18 Jan 2022 16:16:51 +0000 [thread overview]
Message-ID: <20220118161651.GO18506@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <CAL_Jsq+x-q_xOctCCVmzNSwGbWa_uipJ84xa1NCZnjhWSn1vVg@mail.gmail.com>
On Tue, Jan 18, 2022 at 08:39:55AM -0600, Rob Herring wrote:
> On Mon, Jan 17, 2022 at 3:56 AM Charles Keepax > <ckeepax@opensource.cirrus.com> wrote:
> > On Mon, Jan 17, 2022 at 09:26:56AM +0000, Charles Keepax wrote:
> > > On Sat, Jan 15, 2022 at 09:55:23AM -0600, Rob Herring wrote:
> > > > On Fri, Jan 14, 2022 at 5:18 AM Charles Keepax > > > > <ckeepax@opensource.cirrus.com> wrote:
> > Ah ok it seems that flag is only currently used by the pinctrl
> > subsystem, didn't realise that was quite so new and not used
> > anywhere. I guess we probably need to add something to the
> > platform device code to use that flag too, if that is the way we
> > want to run with this.
>
> I pushed a patch[1] for kernel-ci to test if you want to give it a try, too.
Awesome thanks. This seems to fix the issue on my system and
doesn't obviously cause any new issues.
Tested-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
next prev parent reply other threads:[~2022-01-18 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 10:56 ChipIdea USB regression Charles Keepax
2022-01-14 11:18 ` Charles Keepax
2022-01-15 15:55 ` Rob Herring
2022-01-17 9:26 ` Charles Keepax
2022-01-17 9:55 ` Charles Keepax
2022-01-18 14:39 ` Rob Herring
2022-01-18 16:16 ` Charles Keepax [this message]
2022-01-16 10:21 ` Thorsten Leemhuis
2022-01-18 16:53 ` Rob Herring
2022-01-18 17:33 ` Thorsten Leemhuis
2022-01-18 18:37 ` Rob Herring
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=20220118161651.GO18506@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.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).