From: Andrew Morton <akpm@linux-foundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 5469/6165] uffd-common.c:636:28: warning: unused variable 'uffdio_move'
Date: Fri, 8 Dec 2023 10:14:43 -0800 [thread overview]
Message-ID: <20231208101443.e1a153ff6d7d753685af024d@linux-foundation.org> (raw)
In-Reply-To: <CAJuCfpE0rvr1apUmrErS-9=QsfTMWt_P-a3xJLNLOfr75AXytg@mail.gmail.com>
On Fri, 8 Dec 2023 10:09:31 -0800 Suren Baghdasaryan <surenb@google.com> wrote:
>
> Hmm. I still see incorrect version in both mm-unstable and in
> linux-next after fetching and rebasing. Maybe I should check a bit
> later?
Pushed out now.
next prev parent reply other threads:[~2023-12-08 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 10:00 kernel test robot
2023-12-08 17:27 ` Suren Baghdasaryan
2023-12-08 18:05 ` Andrew Morton
2023-12-08 18:06 ` Suren Baghdasaryan
2023-12-08 18:09 ` Suren Baghdasaryan
2023-12-08 18:14 ` Andrew Morton [this message]
2023-12-08 22:17 ` Suren Baghdasaryan
2023-12-08 18:06 ` Suren Baghdasaryan
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=20231208101443.e1a153ff6d7d753685af024d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=surenb@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