From: Michael Ellerman <mpe@ellerman.id.au>
To: Laurent Vivier <lvivier@redhat.com>, linux-kernel@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>,
Christophe Leroy <christophe.leroy@c-s.fr>
Subject: Re: [PATCH v2] powerpc/mm: move a KERN_WARNING message to pr_debug()
Date: Thu, 07 Feb 2019 15:33:57 +1100 [thread overview]
Message-ID: <8736p0kyiy.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20190205202133.5048-1-lvivier@redhat.com>
Hi Laurent,
I'm not sure I'm convinced about this one. It seems like we're just
throwing away the warning because it's annoying.
Laurent Vivier <lvivier@redhat.com> writes:
> resize_hpt_for_hotplug() reports a warning when it cannot
> increase the hash page table ("Unable to resize hash page
> table to target order") but this is not blocking and
> can make user thinks something has not worked properly.
Something did not work properly, the resize didn't work properly. Right?
> As we move the message to the debug area, report again the
> ENODEV error.
>
> If the operation cannot be done the real error message
> will be reported by arch_add_memory() if create_section_mapping()
> fails.
Can you explain that more. Isn't the fact that the resize failed "the
real error message"?
> Fixes: 7339390d772dd
> powerpc/pseries: Don't give a warning when HPT resizing isn't available
This should all be on one line, and formatted as:
Fixes: 7339390d772d ("powerpc/pseries: Don't give a warning when HPT resizing isn't available")
See Documentation/process/submitting-patches.rst for more info and how
to configure git to do it automatically for you.
cheers
next prev parent reply other threads:[~2019-02-07 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 20:21 Laurent Vivier
2019-02-07 3:03 ` David Gibson
2019-02-07 9:25 ` Laurent Vivier
2019-02-07 4:33 ` Michael Ellerman [this message]
2019-02-07 9:13 ` Laurent Vivier
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=8736p0kyiy.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@c-s.fr \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvivier@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
all inboxes | Powered by JetHome®