Re: linux-next: Tree for Apr 29

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux MM <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Apr 29
Date: Mon, 29 Apr 2013 14:03:23 -0700	[thread overview]
Message-ID: <517EE01B.80109@infradead.org> (raw)
In-Reply-To: <517ED2A6.5030200@infradead.org>

On 04/29/13 13:05, Randy Dunlap wrote:
> On 04/29/13 02:17, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130426:
>>
> 
> 
> (who is responsible for MEM_SOFT_DIRTY?)
> 
> 
> on x86_64:
> 
> warning: (HWPOISON_INJECT && MEM_SOFT_DIRTY) selects PROC_PAGE_MONITOR which has unmet direct dependencies (PROC_FS && MMU)
> 
> because MEM_SOFT_DIRTY selects PROC_PAGE_MONITOR when CONFIG_PROC_FS is not enabled.
> 
> 
> Can MEM_SOFT_DIRTY depend on PROC_FS?
> 
> and the help text for MEM_SOFT_DIRTY refers to Documentation/vm/soft-dirty.txt,
> which does not exist.  Please add the file.

Oops, sorry, I looked in the wrong place for that file, which DOES exist.


-- 
~Randy

--
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>

WARNING: multiple messages have this Message-ID (diff)

From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux MM <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Apr 29
Date: Mon, 29 Apr 2013 14:03:23 -0700	[thread overview]
Message-ID: <517EE01B.80109@infradead.org> (raw)
In-Reply-To: <517ED2A6.5030200@infradead.org>

On 04/29/13 13:05, Randy Dunlap wrote:
> On 04/29/13 02:17, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130426:
>>
> 
> 
> (who is responsible for MEM_SOFT_DIRTY?)
> 
> 
> on x86_64:
> 
> warning: (HWPOISON_INJECT && MEM_SOFT_DIRTY) selects PROC_PAGE_MONITOR which has unmet direct dependencies (PROC_FS && MMU)
> 
> because MEM_SOFT_DIRTY selects PROC_PAGE_MONITOR when CONFIG_PROC_FS is not enabled.
> 
> 
> Can MEM_SOFT_DIRTY depend on PROC_FS?
> 
> and the help text for MEM_SOFT_DIRTY refers to Documentation/vm/soft-dirty.txt,
> which does not exist.  Please add the file.

Oops, sorry, I looked in the wrong place for that file, which DOES exist.


-- 
~Randy

next prev parent reply	other threads:[~2013-04-29 21:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29  9:17 linux-next: Tree for Apr 29 Stephen Rothwell
2013-04-29  9:17 ` Stephen Rothwell
2013-04-29 15:52 ` linux-next: Tree for Apr 29 (kvm) Randy Dunlap
2013-04-29 16:31   ` Gleb Natapov
2013-04-29 16:46     ` Paolo Bonzini
2013-04-29 17:01       ` Alex Williamson
2013-04-29 16:49     ` Alex Williamson
2013-04-29 16:05 ` [PATCH -next] proc_fs.h: fix build error when PROC_FS is not enabled Randy Dunlap
2013-04-30 16:36   ` David Rientjes
2013-04-30 17:40     ` Randy Dunlap
2013-04-29 16:05 ` [PATCH -next] tty.h: fix build errors " Randy Dunlap
2013-04-30 16:39   ` David Rientjes
2013-04-29 16:17 ` linux-next: Tree for Apr 29 (include/linux/proc_fs.h: proc_net_mkdir) Randy Dunlap
2013-04-29 16:25 ` linux-next: Tree for Apr 29 (kconfig) Randy Dunlap
2013-04-29 17:42   ` Yann E. MORIN
2013-04-29 16:42 ` linux-next: Tree for Apr 29 (staging/gdm72xx) Randy Dunlap
2013-04-29 16:51 ` linux-next: Tree for Apr 29 (sound/soc) Randy Dunlap
2013-04-29 17:13 ` linux-next: Tree for Apr 29 (many build errors when PROC_FS is not set -- part 1) Randy Dunlap
2013-04-29 20:05 ` linux-next: Tree for Apr 29 Randy Dunlap
2013-04-29 20:05   ` Randy Dunlap
2013-04-29 21:03   ` Randy Dunlap [this message]
2013-04-29 21:03     ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2014-04-29  7:29 Stephen Rothwell
2014-04-29  7:29 ` Stephen Rothwell
2015-04-29  4:27 Stephen Rothwell
2016-04-29  7:13 Stephen Rothwell
2019-04-29  9:03 Stephen Rothwell
2020-04-29  8:33 Stephen Rothwell
2021-04-29  5:27 Stephen Rothwell
2022-04-29  7:31 Stephen Rothwell
2024-04-29  7:20 Stephen Rothwell
2025-04-29  9:02 Stephen Rothwell
2026-04-29 11:27 Thierry Reding

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=517EE01B.80109@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.