From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL v2] PHY: For 5.6
Date: Fri, 17 Jan 2020 19:35:23 +0100 [thread overview]
Message-ID: <20200117183523.GA1968804@kroah.com> (raw)
In-Reply-To: <20200117065426.GA1699866@kroah.com>
On Fri, Jan 17, 2020 at 07:54:26AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Jan 17, 2020 at 11:05:40AM +0530, Kishon Vijay Abraham I wrote:
> > Hi Greg,
> >
> > Please find the updated pull request for 5.6 merge window below.
> >
> > Here I fixed the incorrect commit ID in Fixes tag on one of the
> > patch. Rest of it remains the same as in v1 PR.
>
> Ok, that worked, I've pulled this version now.
I'm getting this build error in my tree now:
Kernel: arch/x86/boot/bzImage is ready (#621)
ERROR: "of_platform_device_destroy" [drivers/phy/ti/phy-j721e-wiz.ko] undefined!
make[1]: *** [scripts/Makefile.modpost:94: __modpost] Error 1
make: *** [Makefile:1282: modules] Error 2
a "depends on" mistake somewhere?
thanks,
greg k-h
prev parent reply other threads:[~2020-01-17 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 5:35 [GIT PULL v2] PHY: For 5.6 Kishon Vijay Abraham I
2020-01-17 6:54 ` Greg Kroah-Hartman
2020-01-17 18:35 ` Greg Kroah-Hartman [this message]
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=20200117183523.GA1968804@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox