From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
<linux-s390@vger.kernel.org>
Subject: Re: [PATCH 3/3] s390: char: make slp_ctl explicitly non-modular
Date: Sun, 30 Oct 2016 12:04:14 -0400 [thread overview]
Message-ID: <20161030160414.GO5641@windriver.com> (raw)
In-Reply-To: <20161030144308.03a804de@mschwide>
[Re: [PATCH 3/3] s390: char: make slp_ctl explicitly non-modular] On 30/10/2016 (Sun 14:43) Martin Schwidefsky wrote:
[...]
> That idea behind the patch makes sense to me. But the built robot
> reports a new warning which should be fixed. If that is done:
>
> Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
The kbuild robot is a false positive ; it test-applied the patches on
master and not on Greg's char-misc ; which as per the 0/3 text is the
whole reason we are putting these patches in via Greg's branch. So
there should be nothing to fix once they are in the right place.
Paul.
--
>
> --
> blue skies,
> Martin.
>
> "Reality continues to ruin my life." - Calvin.
>
prev parent reply other threads:[~2016-10-30 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 20:38 [PATCH 0/3] Add new builtin_misc_device users Paul Gortmaker
2016-10-29 20:38 ` [PATCH 1/3] lightnvm: make core.c explicitly non-modular Paul Gortmaker
2016-10-29 22:01 ` kbuild test robot
2016-10-29 22:36 ` Paul Gortmaker
2016-10-29 20:38 ` [PATCH 2/3] blackfin: make-bf561/coreb.c " Paul Gortmaker
2016-10-30 1:02 ` kbuild test robot
2016-10-29 20:38 ` [PATCH 3/3] s390: char: make slp_ctl " Paul Gortmaker
2016-10-29 22:49 ` kbuild test robot
2016-10-30 13:43 ` Martin Schwidefsky
2016-10-30 16:04 ` Paul Gortmaker [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=20161030160414.GO5641@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.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