From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1759973AbdEYK6I (ORCPT <rfc822;w@1wt.eu>);
        Thu, 25 May 2017 06:58:08 -0400
Received: from mout.web.de ([212.227.15.14]:64010 "EHLO mout.web.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1759617AbdEYK6E (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 25 May 2017 06:58:04 -0400
Subject: Re: MIPS: Alchemy: Delete an error message for a failed memory
 allocation in alchemy_pci_probe()
To: Manuel Lauss <manuel.lauss@gmail.com>, linux-mips@linux-mips.org
Cc: Paul Burton <paul.burton@imgtec.com>,
        =?UTF-8?Q?Ralf_B=c3=a4chle?= <ralf@linux-mips.org>,
        LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
References: <6ebb5193-239f-5c34-c5f6-2be8a2fa79a5@users.sourceforge.net>
 <CAOLZvyHq-7q0XxiBsyX3q0g0J3kjfFv4SU7amX1hpjRDyK+feQ@mail.gmail.com>
 <796029e7-60a3-a94b-8b5c-4686a0656560@users.sourceforge.net>
 <CAOLZvyH-DF_r77kzcVcn+A-tTov+aNZ1oGNQLnGWXE35UODqtQ@mail.gmail.com>
 <70394897-a67a-2b49-2d46-a20fb2de51f2@users.sourceforge.net>
 <CAOLZvyGEzzQ_Jvy3NNQqDER4QHe2Dj-Y4sX2MNANo-phXbzQ8g@mail.gmail.com>
From: SF Markus Elfring <elfring@users.sourceforge.net>
Message-ID: <6769aa4c-3a32-3ce5-fb65-f218016a1aa8@users.sourceforge.net>
Date: Thu, 25 May 2017 12:57:57 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <CAOLZvyGEzzQ_Jvy3NNQqDER4QHe2Dj-Y4sX2MNANo-phXbzQ8g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:xYfpL8Uu51CtUX2uN1wJVv5j2EMvw0uxj1uHE14zusDfggW4v7x
 az2bmh6/gEbrbK3DwLMZd4P95TqJ+xZRvINpeFWiQiPT7XWxO7/XCktcBfm9Yc2YLBuDXHr
 Mf8pX6CX8hG1l1Z9E/SBM29Oxsr4PBoKssx2JUQRtvT1USgRn2/JP5rHVUaBYeT2bAw3k2m
 CwAZafV91c56Dg+6qiGTg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:TtgMRqfCLNg=:7p3cgp2RXhLeMqbLZ7CBV+
 NB9fY+p8hJrfeCo3RF9jwsSfUpuVAF+8/fM8ifeZOuLLr+JI2gw2f32suFI5tGLB2kHoMCka1
 E3ApV7BqUB6Q/+XEtfr76t5IQ7rHTN3WF0R3wxoGHDziRrddIm2/dszQgL2oo5Tv8YANO2U4G
 dGPHYAqmzTop3TMSG8HXxikuMkt7lTa9SxCaHMCaoRhx5eWW1vChtiss6PKWFhaVqFyNSVqga
 tvgICZpf8p5Dc529Ng/9yUzWGmdgv6LG6YmOe225l9j434tV9EE0CH22OdeFw0fMUgmV7Rcib
 F9YeOO54a34CSsk6bhWmklEjUX+unhd4AEErkJ5fW7N21cjsGL8ch4PcI9yPItj4bQhNWUHjP
 rD0G0agCAdtyH37qNCMxnYxxcvaFVqvBxUoTL82a0ImQv7B9fdJUIkgxhheMsvR1jfqAqlJ5h
 84O0Tnx29LPky1PEb0XrN7PcKzt0BxsrW0sBTZPxhmM6iBIVZ1NweHXACinBJqu6pdSjpiZu+
 MB9GoZIGuNPLYI8ac9LZxulfNaApZem1QDF9hc0B+ETwecWyfbtt+JyqFAJLHPhD0D0I7ukhq
 7uq1g51CsYEFUTv+Y2BNviuoLyks5EYz3o1ApYHLhsJgGDwOR2ugbXWAfrx1HNaaTq56Aidb0
 uTDEBEp9ycTFj6L3dWkhfqUGlXBSIX4yMa+DlE0JmHlODfTizRcSNBRwlhkkF8/OgKqtOCvC9
 pz6noe94P+RRhhqOcx2SqIYyzYWMaDOF0WKdqPmQQp8qsLhXNY7AxNQUw5xW+RbsjQicRK1kP
 keQEI6F
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

>> * Why do you seem to insist on another message if information from a Linux
>>   allocation failure report would be sufficient already also for this
>>   software module?
>>
>> * Do you want that it can become easier to map a position in a backtrace
>>   to a place in your source code?
> 
> Does kmalloc() nowadays print a message which invocation (source line) failed?
> If so I won't be standing in your way, but if not, you need to come up with
> something for convincing than answering questions with more questions.

I suggest also to improve the corresponding documentation for the affected
programming interfaces in significant ways.
How are the chances for the desired clarification of relevant implementation details?

Regards,
Markus