From: Jonathan Corbet <corbet@lwn.net>
To: Joe Perches <joe@perches.com>
Cc: Nick Crews <ncrews@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] coding-style.rst: Generic alloc functions do not need OOM logging
Date: Mon, 1 Apr 2019 15:01:50 -0600 [thread overview]
Message-ID: <20190401150150.23d2a0f0@lwn.net> (raw)
In-Reply-To: <5d7229de06286b4ec06daee3411e39e9b638d66c.camel@perches.com>
On Sat, 30 Mar 2019 10:25:03 -0700
Joe Perches <joe@perches.com> wrote:
> Generic allocation functions already emit a dump_stack()
> so additional error logging isn't useful.
>
> Document it as such and add a reference to the allocation
> API.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Applied, thanks.
jon
next prev parent reply other threads:[~2019-04-01 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 17:25 [PATCH] coding-style.rst: Generic alloc functions do not need OOM logging Joe Perches
2019-04-01 21:01 ` Jonathan Corbet [this message]
2019-04-01 21:12 ` Nick Crews
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=20190401150150.23d2a0f0@lwn.net \
--to=corbet@lwn.net \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncrews@chromium.org \
/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).