From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, "Jörg Rödel" <joro@8bytes.org>,
"Will Deacon" <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ARM-SMMU: Delete error messages for a failed memory allocation in three functions
Date: Mon, 22 Jan 2018 19:12:07 +0100 [thread overview]
Message-ID: <a714a4ab-8118-e4ef-5982-4395ac2e6c4b@users.sourceforge.net> (raw)
In-Reply-To: <ac171b23-624d-2df3-d1d1-8e9479ae03bc@arm.com>
>> Date: Sat, 20 Jan 2018 15:30:17 +0100
>>
>> Omit extra messages for a memory allocation failure in these functions.
>
> Why?
Do you find the wording “WARNING: Possible unnecessary 'out of memory' message”
(from the script “checkpatch.pl”) more reasonable?
> This may as well be "delete some stuff because I feel like it".
Do you find the Linux allocation failure report insufficient
in this use case?
Regards,
Markus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-01-22 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 14:36 [PATCH] ARM-SMMU: Delete error messages for a failed memory allocation in three functions SF Markus Elfring
[not found] ` <c3e91414-dd5b-2889-d86c-b19aff56571b-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
2018-01-22 11:47 ` Robin Murphy
[not found] ` <ac171b23-624d-2df3-d1d1-8e9479ae03bc-5wv7dgnIgG8@public.gmane.org>
2018-01-22 11:53 ` Will Deacon
2018-01-22 18:12 ` SF Markus Elfring [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=a714a4ab-8118-e4ef-5982-4395ac2e6c4b@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).