From: David Hildenbrand <david@redhat.com>
To: kernel test robot <lkp@intel.com>, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Michal Hocko <mhocko@suse.com>,
Oscar Salvador <osalvador@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Subject: Re: [PATCH v1 1/2] drivers/base/memory: don't store phys_device in memory blocks
Date: Mon, 1 Feb 2021 14:27:03 +0100 [thread overview]
Message-ID: <616070a6-fcd6-f16d-cbf6-68b8b2a8f5aa@redhat.com> (raw)
In-Reply-To: <202102012056.KCZmZLEr-lkp@intel.com>
[...]
> All warnings (new ones prefixed by >>):
>
> drivers/base/memory.c: In function 'init_memory_block':
>>> drivers/base/memory.c:573:16: warning: variable 'start_pfn' set but not used [-Wunused-but-set-variable]
> 573 | unsigned long start_pfn;
> | ^~~~~~~~~
Indeed, we no longer need start_pfn in init_memory_block().
--
Thanks,
David / dhildenb
WARNING: multiple messages have this Message-ID (diff)
From: David Hildenbrand <david@redhat.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v1 1/2] drivers/base/memory: don't store phys_device in memory blocks
Date: Mon, 01 Feb 2021 14:27:03 +0100 [thread overview]
Message-ID: <616070a6-fcd6-f16d-cbf6-68b8b2a8f5aa@redhat.com> (raw)
In-Reply-To: <202102012056.KCZmZLEr-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
[...]
> All warnings (new ones prefixed by >>):
>
> drivers/base/memory.c: In function 'init_memory_block':
>>> drivers/base/memory.c:573:16: warning: variable 'start_pfn' set but not used [-Wunused-but-set-variable]
> 573 | unsigned long start_pfn;
> | ^~~~~~~~~
Indeed, we no longer need start_pfn in init_memory_block().
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-02-01 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 10:51 [PATCH v1 0/2] drivers/base/memory: clarify some memory block properties David Hildenbrand
2021-02-01 10:51 ` [PATCH v1 1/2] drivers/base/memory: don't store phys_device in memory blocks David Hildenbrand
2021-02-01 13:00 ` kernel test robot
2021-02-01 13:00 ` kernel test robot
2021-02-01 13:27 ` David Hildenbrand [this message]
2021-02-01 13:27 ` David Hildenbrand
2021-02-01 15:58 ` Michal Hocko
2021-02-01 10:51 ` [PATCH v1 2/2] Documentation: sysfs/memory: clarify some memory block device properties David Hildenbrand
2021-02-01 16:00 ` Michal Hocko
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=616070a6-fcd6-f16d-cbf6-68b8b2a8f5aa@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.