From: Jason Baron <jbaron@akamai.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-mm@kvack.org,
Michal Hocko <mhocko@suse.com>
Subject: Re: [memcg:since-4.6 827/827] arch/s390/include/asm/jump_label.h:17:32: error: expected ':' before '__stringify'
Date: Wed, 13 Jul 2016 14:16:11 -0400 [thread overview]
Message-ID: <5786856B.6030600@akamai.com> (raw)
In-Reply-To: <20160713110542.b58b2bcc7ca484a56cb903f3@linux-foundation.org>
On 07/13/2016 02:05 PM, Andrew Morton wrote:
> On Wed, 13 Jul 2016 13:43:44 -0400 Jason Baron <jbaron@akamai.com> wrote:
>
>> This is likely due to the fact that the s390 bits
>> bits were not pulled into -mm here:
>>
>> http://lkml.iu.edu/hypermail/linux/kernel/1607.0/03114.html
>>
>> However, I do see them in linux-next, I think from
>> the s390 tree. So perhaps, that patch can be pulled
>> in here as well?
>
> Yup, I have
> jump_label-remove-bugh-atomich-dependencies-for-have_jump_label.patch
> staged after linux-next and it has that dependency on linux-next.
>
ok, you have the dependency correct, thanks.
That dependency though is not being honored in the referenced
mm tree branch 'since-4.6', since the relevant s390 patch
is not present. So, if we want to fix it here, we need
that patch...
Thanks,
-Jason
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-07-13 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 17:19 kbuild test robot
2016-07-13 17:43 ` Jason Baron
2016-07-13 18:05 ` Andrew Morton
2016-07-13 18:16 ` Jason Baron [this message]
2016-07-14 7:19 ` Michal Hocko
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=5786856B.6030600@akamai.com \
--to=jbaron@akamai.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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