From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Felipe Balbi <balbi@kernel.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [GIT PULL] USB for v5.7 merge window
Date: Mon, 16 Mar 2020 08:26:04 +0100 [thread overview]
Message-ID: <20200316072604.GC3019942@kroah.com> (raw)
In-Reply-To: <87wo7lenor.fsf@kernel.org>
On Sun, Mar 15, 2020 at 03:45:56PM +0200, Felipe Balbi wrote:
>
> Hi,
>
> Man... I did it! I managed to get through all 500+ patches in time. I
> can't believe it.
>
> For everyone involved, I'm sorry for the delay, but I've been super busy
> at work. I genuinely apologize for this and will try to better plan my
> week to guarantee at least 3 hours a week to look at the mailing list.
>
> Greg,
>
> If you want anything to be changed, let me know.
>
> Cheers
>
> The following changes since commit 2c523b344dfa65a3738e7039832044aa133c75fb:
>
> Linux 5.6-rc5 (2020-03-08 17:44:44 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git usb-for-v5.7
Hm, I hit the issue that Stephen also hit with the merge and build
breakage.
Then I hit this problem too:
Commit: 238d76021654 ("usb: dwc3: meson-g12a: Don't use ret uninitialized in dwc3_meson_g12a_otg_init")
Fixes tag: Fixes: 729149c53f04 ("usb: dwc3: Add Amlogic A1 DWC3 glue")
Has these problem(s):
- Target SHA1 does not exist
I'll "override" the failure in my scripts, as I don't want you to have
to rebase your tree, but something is odd there...
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-16 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 13:45 [GIT PULL] USB for v5.7 merge window Felipe Balbi
2020-03-16 7:26 ` Greg Kroah-Hartman [this message]
2020-03-16 7:57 ` Felipe Balbi
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=20200316072604.GC3019942@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.