From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
SF Markus Elfring
<elfring-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM-SMMU: Delete error messages for a failed memory allocation in three functions
Date: Mon, 22 Jan 2018 11:53:31 +0000 [thread overview]
Message-ID: <20180122115331.GE15456@arm.com> (raw)
In-Reply-To: <ac171b23-624d-2df3-d1d1-8e9479ae03bc-5wv7dgnIgG8@public.gmane.org>
On Mon, Jan 22, 2018 at 11:47:13AM +0000, Robin Murphy wrote:
> On 20/01/18 14:36, SF Markus Elfring wrote:
> >From: Markus Elfring <elfring-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
> >Date: Sat, 20 Jan 2018 15:30:17 +0100
> >
> >Omit extra messages for a memory allocation failure in these functions.
>
> Why?
Don't worry -- I was ignoring this patch (and I assume Joerg does the same).
Will
next prev parent reply other threads:[~2018-01-22 11:53 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 [this message]
2018-01-22 18:12 ` SF Markus Elfring
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=20180122115331.GE15456@arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=elfring-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.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).