From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>,
Johannes Thumshirn <jthumshirn@suse.de>,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
bart.vanassche@wdc.com, axboe@kernel.dk,
chris@chris-wilson.co.uk, tvrtko.ursulin@intel.com
Subject: Re: [PATCH] lib/scatterlist: Add SG_CHAIN and SG_EMARK macros for LSB encodings
Date: Thu, 15 Feb 2018 08:23:11 +0530 [thread overview]
Message-ID: <df1466af-c145-5225-c71b-9e0977faa98a@linux.vnet.ibm.com> (raw)
In-Reply-To: <ebbfc01c-3f42-483e-a281-1b4572bc8ac2@ursulin.net>
On 02/14/2018 09:41 PM, Tvrtko Ursulin wrote:
>
> On 14/02/18 08:32, Johannes Thumshirn wrote:
>> On Wed, 2018-02-14 at 10:28 +0530, Anshuman Khandual wrote:
>>> This replaces scatterlist->page_link LSB encodings with SG_CHAIN and
>>> SG_EMARK definitions without any functional change.
>>>
>>> Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
>>> ---
>>> include/linux/scatterlist.h | 23 +++++++++++++----------
>>> 1 file changed, 13 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/include/linux/scatterlist.h
>>> b/include/linux/scatterlist.h
>>> index 22b2131bcdcd..63d00bdb2fb3 100644
>>> --- a/include/linux/scatterlist.h
>>> +++ b/include/linux/scatterlist.h
>>> @@ -65,16 +65,18 @@ struct sg_table {
>>> */
>>> #define SG_MAGIC 0x87654321
>>> +#define SG_CHAIN 0x01
>>> +#define SG_EMARK 0x02
>>
>> SG_EMARK sounds strange, what about SG_END?
>
> +1 on SG_END.
>
> Btw, just a cleanup for readability or you have further work in this area?
Sure, will replace with SG_END. I was trying something else on virtio drivers
on POWER platform and just came across this.
next prev parent reply other threads:[~2018-02-15 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 4:58 Anshuman Khandual
2018-02-14 8:32 ` Johannes Thumshirn
2018-02-14 16:11 ` Tvrtko Ursulin
2018-02-15 2:53 ` Anshuman Khandual [this message]
2018-02-14 16:03 ` Bart Van Assche
2018-02-15 2:54 ` 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=df1466af-c145-5225-c71b-9e0977faa98a@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=chris@chris-wilson.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tursulin@ursulin.net \
--cc=tvrtko.ursulin@intel.com \
/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
all inboxes | Powered by JetHome®