From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?J=F6rg_R=F6del?= Date: Sat, 20 Jan 2018 19:40:05 +0000 Subject: Re: [PATCH] Intel-IOMMU: Delete an error message for a failed memory allocation in init_dmars() Message-Id: <20180120194004.GC28161@8bytes.org> List-Id: References: <20180120133452.GB28161@8bytes.org> <6b452dfb-b2fc-2417-26b3-bbcdf11ed06f@users.sourceforge.net> In-Reply-To: <6b452dfb-b2fc-2417-26b3-bbcdf11ed06f-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: SF Markus Elfring Cc: kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, David Woodhouse , LKML On Sat, Jan 20, 2018 at 03:55:37PM +0100, SF Markus Elfring wrote: > Do you need any more background information for this general > transformation pattern? No. > Do you find the Linux allocation failure report insufficient for this > use case? Yes, because it can't tell me what the code was trying to allocate. From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?J=F6rg_R=F6del?= Subject: Re: [PATCH] Intel-IOMMU: Delete an error message for a failed memory allocation in init_dmars() Date: Sat, 20 Jan 2018 20:40:05 +0100 Message-ID: <20180120194004.GC28161@8bytes.org> References: <20180120133452.GB28161@8bytes.org> <6b452dfb-b2fc-2417-26b3-bbcdf11ed06f@users.sourceforge.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <6b452dfb-b2fc-2417-26b3-bbcdf11ed06f-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: SF Markus Elfring Cc: kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, David Woodhouse , LKML List-Id: iommu@lists.linux-foundation.org On Sat, Jan 20, 2018 at 03:55:37PM +0100, SF Markus Elfring wrote: > Do you need any more background information for this general > transformation pattern? No. > Do you find the Linux allocation failure report insufficient for this > use case? Yes, because it can't tell me what the code was trying to allocate. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756620AbeATTkI (ORCPT ); Sat, 20 Jan 2018 14:40:08 -0500 Received: from 8bytes.org ([81.169.241.247]:54082 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756422AbeATTkG (ORCPT ); Sat, 20 Jan 2018 14:40:06 -0500 Date: Sat, 20 Jan 2018 20:40:05 +0100 From: =?iso-8859-1?Q?J=F6rg_R=F6del?= To: SF Markus Elfring Cc: iommu@lists.linux-foundation.org, David Woodhouse , LKML , kernel-janitors@vger.kernel.org Subject: Re: [PATCH] Intel-IOMMU: Delete an error message for a failed memory allocation in init_dmars() Message-ID: <20180120194004.GC28161@8bytes.org> References: <20180120133452.GB28161@8bytes.org> <6b452dfb-b2fc-2417-26b3-bbcdf11ed06f@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6b452dfb-b2fc-2417-26b3-bbcdf11ed06f@users.sourceforge.net> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 20, 2018 at 03:55:37PM +0100, SF Markus Elfring wrote: > Do you need any more background information for this general > transformation pattern? No. > Do you find the Linux allocation failure report insufficient for this > use case? Yes, because it can't tell me what the code was trying to allocate.