From: Jens Axboe <axboe@kernel•dk>
To: jeffrey.t.kirsher@intel•com,
Anshuman Khandual <anshuman.khandual@arm•com>,
linux-mm@kvack•org, linux-kernel@vger•kernel.org
Cc: linux-block@vger•kernel.org, linux-fbdev@vger•kernel.org,
linux-ia64@vger•kernel.org, linux-rdma@vger•kernel.org,
netdev@vger•kernel.org, iommu@lists•linux-foundation.org,
dri-devel@lists•freedesktop.org, hverkuil@xs4all•nl,
dmaengine@vger•kernel.org, vkoul@kernel•org,
intel-wired-lan@lists•osuosl.org, linux-alpha@vger•kernel.org,
sparclinux@vger•kernel.org, jiangqi903@gmail•com,
akpm@linux-foundation•org, linuxppc-dev@lists•ozlabs.org,
ocfs2-devel@oss•oracle.com, linux-media@vger•kernel.org
Subject: Re: [Intel-wired-lan] [PATCH V2] mm: Replace all open encodings for NUMA_NO_NODE
Date: Mon, 26 Nov 2018 11:04:24 -0700 [thread overview]
Message-ID: <4d0840f2-bd96-e671-8120-56ef33a37816@kernel.dk> (raw)
In-Reply-To: <c1b8de1a8e9d4d215b56498e2d5b83a02083483a.camel@intel.com>
On 11/26/18 10:56 AM, Jeff Kirsher wrote:
> On Mon, 2018-11-26 at 17:56 +0530, Anshuman Khandual wrote:
>> At present there are multiple places where invalid node number is
>> encoded
>> as -1. Even though implicitly understood it is always better to have
>> macros
>> in there. Replace these open encodings for an invalid node number
>> with the
>> global macro NUMA_NO_NODE. This helps remove NUMA related assumptions
>> like
>> 'invalid node' from various places redirecting them to a common
>> definition.
>>
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm•com>
>
> For the 'ixgbe' driver changes.
>
> Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel•com>
Lost the original, but for mtip32xx:
Acked-by: Jens Axboe <axboe@kernel•dk>
--
Jens Axboe
next prev parent reply other threads:[~2018-11-26 18:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 12:26 [PATCH V2] mm: Replace all open encodings for NUMA_NO_NODE Anshuman Khandual
2018-11-26 12:48 ` David Hildenbrand
2018-11-26 14:02 ` Anshuman Khandual
2018-11-26 17:56 ` [Intel-wired-lan] " Jeff Kirsher
2018-11-26 18:04 ` Jens Axboe [this message]
2018-11-27 7:57 ` Michael Ellerman
2018-11-27 13:58 ` Vinod Koul
2018-12-03 18:59 ` Doug Ledford
2018-12-04 21:26 ` Lubomir Rintel
2018-12-05 11:31 ` Anshuman Khandual
2018-12-05 11:47 ` Lubomir Rintel
2018-12-05 5:00 ` [LKP] [mm] 19717e78a0: stderr.if(target_node==NUMA_NO_NODE){ kernel test robot
2018-12-05 11:20 ` Anshuman Khandual
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=4d0840f2-bd96-e671-8120-56ef33a37816@kernel.dk \
--to=axboe@kernel$(echo .)dk \
--cc=akpm@linux-foundation$(echo .)org \
--cc=anshuman.khandual@arm$(echo .)com \
--cc=dmaengine@vger$(echo .)kernel.org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=hverkuil@xs4all$(echo .)nl \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=iommu@lists$(echo .)linux-foundation.org \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=jiangqi903@gmail$(echo .)com \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-block@vger$(echo .)kernel.org \
--cc=linux-fbdev@vger$(echo .)kernel.org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ocfs2-devel@oss$(echo .)oracle.com \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=vkoul@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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