From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Manuel Lauss <manuel.lauss@gmail.com>, linux-mips@linux-mips.org
Cc: "Paul Burton" <paul.burton@imgtec.com>,
"Ralf Bächle" <ralf@linux-mips.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_probe()
Date: Thu, 25 May 2017 10:57:57 +0000 [thread overview]
Message-ID: <6769aa4c-3a32-3ce5-fb65-f218016a1aa8@users.sourceforge.net> (raw)
In-Reply-To: <CAOLZvyGEzzQ_Jvy3NNQqDER4QHe2Dj-Y4sX2MNANo-phXbzQ8g@mail.gmail.com>
>> * 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
prev parent reply other threads:[~2017-05-25 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 16:42 [PATCH] MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_probe() SF Markus Elfring
2017-05-24 17:42 ` [PATCH] MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_pro Manuel Lauss
2017-05-24 18:15 ` SF Markus Elfring
2017-05-24 18:26 ` Randy Dunlap
2017-05-24 20:26 ` MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_probe() SF Markus Elfring
2017-05-25 6:20 ` [PATCH] MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_pro Manuel Lauss
2017-05-25 6:54 ` MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_probe() SF Markus Elfring
2017-05-25 9:29 ` Manuel Lauss
2017-05-25 10:57 ` 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=6769aa4c-3a32-3ce5-fb65-f218016a1aa8@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.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