From: Pavel Tatashin <pasha.tatashin@oracle.com>
To: osalvador@techadventures.net
Cc: Steven Sistare <steven.sistare@oracle.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kirill.shutemov@linux.intel.com, Michal Hocko <mhocko@suse.com>,
Linux Memory Management List <linux-mm@kvack.org>,
dan.j.williams@intel.com, jack@suse.cz, jglisse@redhat.com,
Souptick Joarder <jrdr.linux@gmail.com>,
bhe@redhat.com, gregkh@linuxfoundation.org,
Vlastimil Babka <vbabka@suse.cz>,
Wei Yang <richard.weiyang@gmail.com>,
dave.hansen@intel.com, rientjes@google.com, mingo@kernel.org
Subject: Re: [PATCH v1 2/2] mm/sparse: start using sparse_init_nid(), and remove old code
Date: Fri, 29 Jun 2018 11:55:59 -0400 [thread overview]
Message-ID: <CAGM2reZV7tG0FEZV94_-6EXxBEwXkZSuoSn93M=8s4VmRNDCPA@mail.gmail.com> (raw)
In-Reply-To: <20180629144059.GB23545@techadventures.net>
> besides this first for_each_present_section_nr(), what about writing a static inline
> function that returns next_present_section_nr(-1) ?
>
> Something like:
>
> static inline int first_present_section_nr(void)
> {
> return next_present_section_nr(-1);
> }
Good idea, will add it, thank you.
Pavel
prev parent reply other threads:[~2018-06-29 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 17:30 [PATCH v1 0/2] sparse_init rewrite Pavel Tatashin
2018-06-28 17:30 ` [PATCH v1 1/2] mm/sparse: add sparse_init_nid() Pavel Tatashin
2018-06-29 10:04 ` Oscar Salvador
2018-06-29 10:44 ` Oscar Salvador
2018-06-29 11:56 ` Pavel Tatashin
2018-06-29 14:35 ` Oscar Salvador
2018-06-29 15:54 ` Pavel Tatashin
2018-06-28 17:30 ` [PATCH v1 2/2] mm/sparse: start using sparse_init_nid(), and remove old code Pavel Tatashin
2018-06-29 14:40 ` Oscar Salvador
2018-06-29 15:55 ` Pavel Tatashin [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='CAGM2reZV7tG0FEZV94_-6EXxBEwXkZSuoSn93M=8s4VmRNDCPA@mail.gmail.com' \
--to=pasha.tatashin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.m.jordan@oracle.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=jrdr.linux@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=osalvador@techadventures.net \
--cc=richard.weiyang@gmail.com \
--cc=rientjes@google.com \
--cc=steven.sistare@oracle.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).