linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: linmiaohe <linmiaohe@huawei.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	"rppt@linux.ibm.com" <rppt@linux.ibm.com>,
	"jannh@google.com" <jannh@google.com>,
	"steve.capper@arm.com" <steve.capper@arm.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"aarcange@redhat.com" <aarcange@redhat.com>,
	"walken@google.com" <walken@google.com>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"tiny.windzz@gmail.com" <tiny.windzz@gmail.com>,
	"jhubbard@nvidia.com" <jhubbard@nvidia.com>,
	"david@redhat.com" <david@redhat.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Wei Yang <richardw.yang@linux.intel.com>
Subject: Re: [PATCH v4] mm: get rid of odd jump labels in find_mergeable_anon_vma()
Date: Sat, 30 Nov 2019 09:12:42 +0100	[thread overview]
Message-ID: <AC5F0A85-74BC-4F7B-8C09-33A1F87564B3@redhat.com> (raw)
In-Reply-To: <0db7574905b64d47a7c88766081fa0ad@huawei.com>



> Am 30.11.2019 um 08:23 schrieb linmiaohe <linmiaohe@huawei.com>:
> 
> 
>> 
>>> From: Miaohe Lin <linmiaohe@huawei.com>
>>> 
>>> The jump labels try_prev and none are not really needed in 
>>> find_mergeable_anon_vma(), eliminate them to improve readability.
>>> 
>>> Reviewed-by: David Hildenbrand <david@redhat.com>
>>> Reviewed-by: John Hubbard <jhubbard@nvidia.com>
>>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> 
>> Reviewed-by: Wei Yang <richardw.yang@linux.intel.com>
> friendly ping ...
> 

We‘re currently in the merge phase, and U.S.A. just had Thanksgiving - so it might take some time to get picked up. Cheers!



  reply	other threads:[~2019-11-30  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-30  7:23 [PATCH v4] mm: get rid of odd jump labels in find_mergeable_anon_vma() linmiaohe
2019-11-30  8:12 ` David Hildenbrand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-30  8:38 linmiaohe
2019-11-18 12:24 linmiaohe
2019-11-18 13:22 ` Wei Yang
2019-11-18 13:48 ` David Hildenbrand
2019-11-18 21:22 ` David Rientjes

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=AC5F0A85-74BC-4F7B-8C09-33A1F87564B3@redhat.com \
    --to=david@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=jannh@google.com \
    --cc=jhubbard@nvidia.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=richardw.yang@linux.intel.com \
    --cc=rppt@linux.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=steve.capper@arm.com \
    --cc=tiny.windzz@gmail.com \
    --cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).