From: Michal Hocko <mhocko@kernel.org>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
richard -rw- weinberger <richard.weinberger@gmail.com>
Subject: Re: mmotm 2018-02-21-14-48 uploaded (mm/page_alloc.c on UML)
Date: Thu, 22 Feb 2018 13:59:55 +0100 [thread overview]
Message-ID: <20180222125955.GD30681@dhcp22.suse.cz> (raw)
In-Reply-To: <20180222103832.GA11623@vmlxhi-102.adit-jv.com>
On Thu 22-02-18 11:38:32, Eugeniu Rosca wrote:
> Hi Michal,
>
> Please, let me know if any action is expected from my end.
I do not thing anything is really needed right now. If you have a strong
opinion about the solution (ifdef vs. noop stub) then speak up.
> Thank you for your support and sorry for the ifdef troubles.
No troubles at all. It was me who pushed you this direction...
--
Michal Hocko
SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
richard -rw- weinberger <richard.weinberger@gmail.com>
Subject: Re: mmotm 2018-02-21-14-48 uploaded (mm/page_alloc.c on UML)
Date: Thu, 22 Feb 2018 13:59:55 +0100 [thread overview]
Message-ID: <20180222125955.GD30681@dhcp22.suse.cz> (raw)
In-Reply-To: <20180222103832.GA11623@vmlxhi-102.adit-jv.com>
On Thu 22-02-18 11:38:32, Eugeniu Rosca wrote:
> Hi Michal,
>
> Please, let me know if any action is expected from my end.
I do not thing anything is really needed right now. If you have a strong
opinion about the solution (ifdef vs. noop stub) then speak up.
> Thank you for your support and sorry for the ifdef troubles.
No troubles at all. It was me who pushed you this direction...
--
Michal Hocko
SUSE Labs
--
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:[~2018-02-22 13:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 22:48 mmotm 2018-02-21-14-48 uploaded akpm
2018-02-21 22:48 ` akpm
2018-02-21 23:58 ` mmotm 2018-02-21-14-48 uploaded (mm/page_alloc.c on UML) Randy Dunlap
2018-02-21 23:58 ` Randy Dunlap
2018-02-22 7:20 ` Michal Hocko
2018-02-22 7:20 ` Michal Hocko
2018-02-22 10:38 ` Eugeniu Rosca
2018-02-22 10:38 ` Eugeniu Rosca
2018-02-22 10:38 ` Eugeniu Rosca
2018-02-22 12:59 ` Michal Hocko [this message]
2018-02-22 12:59 ` Michal Hocko
2018-02-22 13:08 ` Eugeniu Rosca
2018-02-22 13:08 ` Eugeniu Rosca
2018-02-22 13:08 ` Eugeniu Rosca
2018-02-22 13:26 ` Michal Hocko
2018-02-22 13:26 ` Michal Hocko
2018-02-25 0:50 ` Eugeniu Rosca
2018-02-25 0:50 ` Eugeniu Rosca
2018-02-25 0:50 ` Eugeniu Rosca
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=20180222125955.GD30681@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=richard.weinberger@gmail.com \
--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.