From: Felipe Balbi <balbi@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [GIT PULL] USB/Thunderbolt/PHY patches for 5.6-rc1
Date: Thu, 30 Jan 2020 12:52:55 +0200 [thread overview]
Message-ID: <87ftfx8bco.fsf@kernel.org> (raw)
In-Reply-To: <20200130083459.206fc0d9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Hi,
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> On Wed, 29 Jan 2020 10:11:26 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>>
>> Stephen, does linux-next perhaps miss these config-time warnings?
>
> I saw it when it first happened and reported it, but since I merge the
> ic2 tree before the usb tree, the warning went away for me after the
> fix was added to the i2c tree.
I wonder if we should start shuffling the order of merges in
linux-next in order to have a chance of finding these issues.
cheers
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-01-30 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 10:14 [GIT PULL] USB/Thunderbolt/PHY patches for 5.6-rc1 Greg KH
2020-01-29 18:11 ` Linus Torvalds
2020-01-29 18:20 ` Krzysztof Kozlowski
2020-01-29 18:23 ` Linus Torvalds
2020-01-29 18:27 ` Krzysztof Kozlowski
2020-01-29 19:42 ` Greg KH
2020-01-29 21:34 ` Stephen Rothwell
2020-01-30 10:52 ` Felipe Balbi [this message]
2020-01-29 19:00 ` pr-tracker-bot
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=87ftfx8bco.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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