From: Greg KH <gregkh@linuxfoundation.org>
To: peng.hao2@zte.com.cn
Cc: arnd@arndb.de, andy.shevchenko@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc/pvpanic: resolve compile errors for arch=um
Date: Tue, 27 Nov 2018 08:58:58 +0100 [thread overview]
Message-ID: <20181127075858.GB929@kroah.com> (raw)
In-Reply-To: <201811271547282511023@zte.com.cn>
On Tue, Nov 27, 2018 at 03:47:28PM +0800, peng.hao2@zte.com.cn wrote:
> >> >On Fri, Nov 16, 2018 at 07:13:26PM +0800, Peng Hao wrote:
> >> >> Resolve compile error for arch=um
> >> >> pvpanic.c:(.text+0xb6): undefined reference to `devm_ioremap_resource'
> >> >>
> >> >> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> >> >> ---
> >> >> drivers/misc/Kconfig | 2 +-
> >> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> >What commit is this fixing? What broke and when did it break?
> >> kbuildtestrobot reports this compile error for arch=um.
> >> here is content:
> >> " head: 24438e46268c721e14c5c888386af85c9e1c5db1
> >> commit: 77703e0b0326a1fb06b5cb5b468a633472c5a8e9 [10/26] misc/pvpanic : break dependency on ACPI
> >
> >Ah, it is breaking because of your patch, not a patch in the kernel
> >today. So please integrate this patch into your latest patch series
> >when you redo your patches.
> >
> The series of patches has merged into "char-misc-next"
> (https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/log/?h=char-misc-next),
> Do I need to re-send the entire series of patches ?
Ah, I didn't realize that. Ok, let me go dig this back up and add it
to my tree, sorry for the noise...
greg k-h
prev parent reply other threads:[~2018-11-27 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 11:13 [PATCH] misc/pvpanic: resolve compile errors for arch=um Peng Hao
2018-11-26 19:53 ` Greg KH
[not found] ` <201811270827031748068@zte.com.cn>
2018-11-27 7:24 ` Greg KH
[not found] ` <201811271547282511023@zte.com.cn>
2018-11-27 7:58 ` Greg KH [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=20181127075858.GB929@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.hao2@zte.com.cn \
/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