[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6303be366cd5b_1b3229487@dwillia2-xfh.jf.intel.com.notmuch>
Date: Mon, 22 Aug 2022 10:34:46 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Adam Manzanares <a.manzanares@...sung.com>,
"alison.schofield@...el.com" <alison.schofield@...el.com>,
"vishal.l.verma@...el.com" <vishal.l.verma@...el.com>,
"ira.weiny@...el.com" <ira.weiny@...el.com>,
"widawsk@...nel.org" <widawsk@...nel.org>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>
CC: "dave@...olabs.net" <dave@...olabs.net>,
"Jonathan.Cameron@...wei.com" <Jonathan.Cameron@...wei.com>,
"linux-cxl@...r.kernel.org" <linux-cxl@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Adam Manzanares <a.manzanares@...sung.com>
Subject: RE: [PATCH] cxl: Replace HDM decoder granularity magic numbers
Adam Manzanares wrote:
> When reviewing the CFMWS parsing code that deals with the HDM decoders,
> I noticed a couple of magic numbers. This commit replaces these magic numbers
> with constants defined by the CXL 2.0 specification.
I have a small quibble with CXL_DECODER_MAX_GRANULARITY_ORDER. How about
CXL_DECODER_MAX_ENCODED_IG? Because the value is not the 'power of 2
order' it's the 'power of 2 order - 8'.
Powered by blists - more mailing lists