From: David Hildenbrand <david@redhat.com>
To: Barry Song <21cnbao@gmail.com>, Chris Li <chrisl@kernel.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, hughd@google.com,
justinjiang@vivo.com, kaleshsingh@google.com, kasong@tencent.com,
linux-kernel@vger.kernel.org, ryan.roberts@arm.com,
v-songbaohua@oppo.com, ying.huang@intel.com
Subject: Re: [PATCH v3 1/2] mm: rename instances of swap_info_struct to meaningful 'si'
Date: Thu, 8 Aug 2024 10:10:25 +0200 [thread overview]
Message-ID: <7d7dd1d2-0c5f-49d4-b3ca-39115f67d2d8@redhat.com> (raw)
In-Reply-To: <CAGsJ_4z=sCyYU9z-HGN=G3wDkoEFrXPXm9nwPnqJhjvjHjufTw@mail.gmail.com>
On 08.08.24 02:21, Barry Song wrote:
> On Thu, Aug 8, 2024 at 12:01 PM Chris Li <chrisl@kernel.org> wrote:
>>
>> On Wed, Aug 7, 2024 at 2:59 PM Barry Song <21cnbao@gmail.com> wrote:
>>>
>>> From: Barry Song <v-songbaohua@oppo.com>
>>>
>>> "p" means "pointer to something", rename it to a more meaningful
>>> identifier - "si".
>>
>> Hi Berry,
>>
>> I am fine with the reason for renaming it to something more
>> meaningful. On the other hand this will create a huge conflict on the
>> next iteration of the swap allocator series. There is not much urgency
>> in the renaming variable, right? Just try to figure out a way to
>> coordinate it better. As it is, I am not sure how to handle the next
>> refresh of swap allocator series, should I revert the rename or submit
>> a refresh of patches with rename conflict resolved, effectively foldin
>> the rename patch.
>
> right, it is not urgent. if you are going to make another iteration
> for the swap allocation series. I am perfect fine that you can add
> these two patches into your series? it should be fine as this patchset
> obviously depends on Kairui's and Your work.
If it can be resolved within 5min of merging I think we shouldn't bother
about delaying this.
I assume it can be resolved within 5min of merging ;)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-08-08 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 21:58 [PATCH v3 0/2] mm: batch free swaps for zap_pte_range() Barry Song
2024-08-07 21:58 ` [PATCH v3 1/2] mm: rename instances of swap_info_struct to meaningful 'si' Barry Song
2024-08-08 0:01 ` Chris Li
2024-08-08 0:21 ` Barry Song
2024-08-08 8:10 ` David Hildenbrand [this message]
2024-08-07 21:58 ` [PATCH v3 2/2] mm: attempt to batch free swap entries for zap_pte_range() Barry Song
2024-08-08 8:14 ` David Hildenbrand
2024-08-15 18:29 ` Chris Li
2024-08-15 21:53 ` Barry Song
2024-08-25 20:09 ` Hugh Dickins
2024-08-25 23:52 ` Barry Song
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=7d7dd1d2-0c5f-49d4-b3ca-39115f67d2d8@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chrisl@kernel.org \
--cc=hughd@google.com \
--cc=justinjiang@vivo.com \
--cc=kaleshsingh@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=v-songbaohua@oppo.com \
--cc=ying.huang@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®