From mboxrd@z Thu Jan 1 00:00:00 1970 From: SF Markus Elfring Date: Wed, 26 Apr 2017 19:14:45 +0000 Subject: Re: Checking error messages for failed memory allocations Message-Id: <16e0c970-1071-ae4b-84fc-952b1fc700f4@users.sourceforge.net> List-Id: References: <75622f45-f46c-e52f-2b9e-6ff5ce32184a@users.sourceforge.net> <3d355c13-159a-2570-9ead-af93ad95c210@users.sourceforge.net> <019b6365c15b0764c156d6453648f7a2@codeaurora.org> <1493231242.18659.28.camel@perches.com> <1493233549.18659.33.camel@perches.com> In-Reply-To: <1493233549.18659.33.camel@perches.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Joe Perches Cc: Subhash Jadavani , linux-scsi@vger.kernel.org, "James E. J. Bottomley" , "Martin K. Petersen" , Vinayak Holikatti , LKML , kernel-janitors@vger.kernel.org, Wolfram Sang , linux-scsi-owner@vger.kernel.org > Feel free to submit documentation patches. Do involved software developers agree on the functionality for stack dumps because of out of memory situations? Regards, Markus