public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/mm: Silence compiler warning when compiling without CONFIG_PGSTE
Date: Mon, 8 Apr 2019 15:28:23 +0200	[thread overview]
Message-ID: <20190408132823.GA13200@osiris> (raw)
In-Reply-To: <84da6d4e-9b85-1c3b-4f48-bdb19ac7f650@redhat.com>

On Mon, Apr 08, 2019 at 12:36:32PM +0200, Thomas Huth wrote:
> On 08/04/2019 09.09, David Hildenbrand wrote:
> > On 07.04.19 14:55, Thomas Huth wrote:
> >> If CONFIG_PGSTE is not set (e.g. when compiling without KVM), GCC complains:
> >>
> >>   CC      arch/s390/mm/pgtable.o
> >> arch/s390/mm/pgtable.c:413:15: warning: ‘pmd_alloc_map’ defined but not
> >>  used [-Wunused-function]
> >>  static pmd_t *pmd_alloc_map(struct mm_struct *mm, unsigned long addr)
> >>                ^~~~~~~~~~~~~
> >>
> >> Wrap the function with "#ifdef CONFIG_PGSTE" to silence the warning.
> >>
> >> Signed-off-by: Thomas Huth <thuth@redhat.com>
> >> ---
> >>  arch/s390/mm/pgtable.c | 2 ++
> >>  1 file changed, 2 insertions(+)
> >>
> >> diff --git a/arch/s390/mm/pgtable.c b/arch/s390/mm/pgtable.c
> >> index 8485d6dc2754..9ebd01219812 100644
> >> --- a/arch/s390/mm/pgtable.c
> >> +++ b/arch/s390/mm/pgtable.c
> >> @@ -410,6 +410,7 @@ static inline pmd_t pmdp_flush_lazy(struct mm_struct *mm,
> >>  	return old;
> >>  }
> >>  
> >> +#ifdef CONFIG_PGSTE
> >>  static pmd_t *pmd_alloc_map(struct mm_struct *mm, unsigned long addr)
> >>  {
> >>  	pgd_t *pgd;
> >> @@ -427,6 +428,7 @@ static pmd_t *pmd_alloc_map(struct mm_struct *mm, unsigned long addr)
> >>  	pmd = pmd_alloc(mm, pud, addr);
> >>  	return pmd;
> >>  }
> >> +#endif
> >>  
> > 
> > We could also move the function down to the functions where it is used
> 
> Yeah, I thought about that, too. Both have advantages:
> 
> - If we keep the code here, "git blame" shows a nicer history of these
>   lines
> - If we move the code, we need less #ifdefs
> 
> I'll leave the decision to the maintainers... Martin, Heiko?

Applied without changes. Thanks!


      reply	other threads:[~2019-04-08 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 12:55 [PATCH] s390/mm: Silence compiler warning when compiling without CONFIG_PGSTE Thomas Huth
2019-04-08  7:09 ` David Hildenbrand
2019-04-08 10:36   ` Thomas Huth
2019-04-08 13:28     ` Heiko Carstens [this message]

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=20190408132823.GA13200@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=thuth@redhat.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