All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vaishali Thakkar <vaishali.thakkar@oracle.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, n-horiguchi@ah.jp.nec.com,
	mike.kravetz@oracle.com, hillf.zj@alibaba-inc.com,
	baiyaowei@cmss.chinamobile.com, dingel@linux.vnet.ibm.com,
	kirill.shutemov@linux.intel.com, dave.hansen@linux.intel.com,
	paul.gortmaker@windriver.com, catalin.marinas@arm.com,
	will.deacon@arm.com, cmetcalf@ezchip.com,
	linux-arm-kernel@lists.infradead.org, james.hogan@imgtec.com,
	linux-metag@vger.kernel.org, benh@kernel.crashing.org,
	paulus@samba.org, mpe@ellerman.id.au,
	linuxppc-dev@lists.ozlabs.org, tglx@linutronix.de,
	mingo@redhat.com, hpa@zytor.com, x86@kernel.org
Subject: Re: [PATCH v2 0/6] mm/hugetlb: Fix commandline parsing behavior for invalid hugepagesize
Date: Wed, 23 Mar 2016 21:31:39 +0530	[thread overview]
Message-ID: <56F2BDE3.40309@oracle.com> (raw)
In-Reply-To: <20160323133011.GG7059@dhcp22.suse.cz>



On Wednesday 23 March 2016 07:00 PM, Michal Hocko wrote:
> On Wed 23-03-16 17:37:18, Vaishali Thakkar wrote:
>> Current code fails to ignore the 'hugepages=' parameters when unsupported
>> hugepagesize is specified. With this patchset, introduce new architecture
>> independent routine hugetlb_bad_size to handle such command line options.
>> And then call it in architecture specific code.
>>
>> Changes since v1:
>> 	- Separated different architecture specific changes in different
>> 	  patches
>> 	- CC'ed all arch maintainers
> The hugetlb parameters parsing is a bit mess but this at least makes it
> behave more consistently. Feel free to add to all patches
> Acked-by: Michal Hocko <mhocko@suse.com>
>
> On a side note. I have received patches with broken threading - the
> follow up patches are not in the single thread under this cover email.
> I thought this was the default behavior of git send-email but maybe your
> (older) version doesn't do that. --thread option would enforce that
> (with --no-chain-reply-to) or you can set it up in the git config. IMHO
> it is always better to have the patchset in the single email thread.
>
Yes, now I have set up my git config for that. Hopefully, things will
work properly - patchset in a single thread from the next time.

Thanks.

-- 
Vaishali

--
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: Vaishali Thakkar <vaishali.thakkar@oracle.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, n-horiguchi@ah.jp.nec.com,
	mike.kravetz@oracle.com, hillf.zj@alibaba-inc.com,
	baiyaowei@cmss.chinamobile.com, dingel@linux.vnet.ibm.com,
	kirill.shutemov@linux.intel.com, dave.hansen@linux.intel.com,
	paul.gortmaker@windriver.com, catalin.marinas@arm.com,
	will.deacon@arm.com, cmetcalf@ezchip.com,
	linux-arm-kernel@lists.infradead.org, james.hogan@imgtec.com,
	linux-metag@vger.kernel.org, benh@kernel.crashing.org,
	paulus@samba.org, mpe@ellerman.id.au,
	linuxppc-dev@lists.ozlabs.org, tglx@linutronix.de,
	mingo@redhat.com, hpa@zytor.com, x86@kernel.org
Subject: Re: [PATCH v2 0/6] mm/hugetlb: Fix commandline parsing behavior for invalid hugepagesize
Date: Wed, 23 Mar 2016 21:31:39 +0530	[thread overview]
Message-ID: <56F2BDE3.40309@oracle.com> (raw)
In-Reply-To: <20160323133011.GG7059@dhcp22.suse.cz>



On Wednesday 23 March 2016 07:00 PM, Michal Hocko wrote:
> On Wed 23-03-16 17:37:18, Vaishali Thakkar wrote:
>> Current code fails to ignore the 'hugepages=' parameters when unsupported
>> hugepagesize is specified. With this patchset, introduce new architecture
>> independent routine hugetlb_bad_size to handle such command line options.
>> And then call it in architecture specific code.
>>
>> Changes since v1:
>> 	- Separated different architecture specific changes in different
>> 	  patches
>> 	- CC'ed all arch maintainers
> The hugetlb parameters parsing is a bit mess but this at least makes it
> behave more consistently. Feel free to add to all patches
> Acked-by: Michal Hocko <mhocko@suse.com>
>
> On a side note. I have received patches with broken threading - the
> follow up patches are not in the single thread under this cover email.
> I thought this was the default behavior of git send-email but maybe your
> (older) version doesn't do that. --thread option would enforce that
> (with --no-chain-reply-to) or you can set it up in the git config. IMHO
> it is always better to have the patchset in the single email thread.
>
Yes, now I have set up my git config for that. Hopefully, things will
work properly - patchset in a single thread from the next time.

Thanks.

-- 
Vaishali

WARNING: multiple messages have this Message-ID (diff)
From: vaishali.thakkar@oracle.com (Vaishali Thakkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] mm/hugetlb: Fix commandline parsing behavior for invalid hugepagesize
Date: Wed, 23 Mar 2016 21:31:39 +0530	[thread overview]
Message-ID: <56F2BDE3.40309@oracle.com> (raw)
In-Reply-To: <20160323133011.GG7059@dhcp22.suse.cz>



On Wednesday 23 March 2016 07:00 PM, Michal Hocko wrote:
> On Wed 23-03-16 17:37:18, Vaishali Thakkar wrote:
>> Current code fails to ignore the 'hugepages=' parameters when unsupported
>> hugepagesize is specified. With this patchset, introduce new architecture
>> independent routine hugetlb_bad_size to handle such command line options.
>> And then call it in architecture specific code.
>>
>> Changes since v1:
>> 	- Separated different architecture specific changes in different
>> 	  patches
>> 	- CC'ed all arch maintainers
> The hugetlb parameters parsing is a bit mess but this at least makes it
> behave more consistently. Feel free to add to all patches
> Acked-by: Michal Hocko <mhocko@suse.com>
>
> On a side note. I have received patches with broken threading - the
> follow up patches are not in the single thread under this cover email.
> I thought this was the default behavior of git send-email but maybe your
> (older) version doesn't do that. --thread option would enforce that
> (with --no-chain-reply-to) or you can set it up in the git config. IMHO
> it is always better to have the patchset in the single email thread.
>
Yes, now I have set up my git config for that. Hopefully, things will
work properly - patchset in a single thread from the next time.

Thanks.

-- 
Vaishali

  reply	other threads:[~2016-03-23 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 12:07 [PATCH v2 0/6] mm/hugetlb: Fix commandline parsing behavior for invalid hugepagesize Vaishali Thakkar
2016-03-23 12:07 ` Vaishali Thakkar
2016-03-23 12:07 ` Vaishali Thakkar
     [not found] ` <1458734844-14833-1-git-send-email-vaishali.thakkar-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-03-23 13:30   ` Michal Hocko
2016-03-23 13:30     ` Michal Hocko
2016-03-23 13:30     ` Michal Hocko
2016-03-23 13:30     ` Michal Hocko
2016-03-23 16:01     ` Vaishali Thakkar [this message]
2016-03-23 16:01       ` Vaishali Thakkar
2016-03-23 16:01       ` Vaishali Thakkar

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=56F2BDE3.40309@oracle.com \
    --to=vaishali.thakkar@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baiyaowei@cmss.chinamobile.com \
    --cc=benh@kernel.crashing.org \
    --cc=catalin.marinas@arm.com \
    --cc=cmetcalf@ezchip.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dingel@linux.vnet.ibm.com \
    --cc=hillf.zj@alibaba-inc.com \
    --cc=hpa@zytor.com \
    --cc=james.hogan@imgtec.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-metag@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhocko@kernel.org \
    --cc=mike.kravetz@oracle.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulus@samba.org \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.com \
    --cc=x86@kernel.org \
    /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.