Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932743AbdDZSMA (ORCPT ); Wed, 26 Apr 2017 14:12:00 -0400 Received: from mout.web.de ([212.227.17.11]:50493 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932715AbdDZSLw (ORCPT ); Wed, 26 Apr 2017 14:11:52 -0400 Subject: Re: scsi: ufs: Delete an error message for a failed memory allocation in ufshcd_memory_alloc() To: Subhash Jadavani Cc: 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 References: <75622f45-f46c-e52f-2b9e-6ff5ce32184a@users.sourceforge.net> <3d355c13-159a-2570-9ead-af93ad95c210@users.sourceforge.net> <019b6365c15b0764c156d6453648f7a2@codeaurora.org> From: SF Markus Elfring Message-ID: <6d4cb083-7a06-3c7d-bf98-a0386178a65d@users.sourceforge.net> Date: Wed, 26 Apr 2017 20:11:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <019b6365c15b0764c156d6453648f7a2@codeaurora.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:+6rckWk/jKvOGxUYHEyDtMkg0GwRlKpOicq29oiGqkH+efUQEfE HLhLWRwNpkdDfjEpbeZtl8cKZtQICqrQn4lXLitYLoqu+lLxCbGZycUlYemB4x3/Eh9+Ffo 0cjOTbMLfGL5/FqAyXfvcWhgASMT3tq62z/0n+sqnkaD65POLqDZKKut1elYjPz0twKfGL3 0eSR9ycyDtILlyLzvAnyA== X-UI-Out-Filterresults: notjunk:1;V01:K0:KoqOZpBWWh8=:qcvma6fSwXOjHjjgiVYJMA pURXb9pLC1W4EPAaKPkzzojMY65B/seW2qELhwGdjGyF0UTgtGJ4NnYqm5HNPGoNWqJjbODs0 M2ujQU7FuEmYHt58xmzreW5ZYGDgR9Knl6FXLNGxdxGazQo1/W4xg8uyogaegXttYgOjW2mPj OrlKL7hk246WSEeOWi6aESR71W1w5stwGb+Sh20CdNE4AESAAIkdbuaZYSFnggcrM6YNCU7fD QUMazu7Kdxr2DxlQftKrWPDezeAnOvMFnM0J0lm0uBXuUtw3KzE4/zyMEbWDfPjEwk1GCGkxc QmUPKHGj7UyRdpLL5wAhIJDPhLsSs4/vDXN5sixFBxwmR1h0i+jvUJMOWOIsUADD59dKWx43l NdyZcnrCmgOnIx/2KTfPl6a4reAm5e7im03bp4+PSS8fi413N0e1gyKwcxTIBguX++lhJQShw 5Gxyrbyxmx/ksPCqSkLfZP1UtXaiQlJFmA2qHQkn6wZArsayBcj5pC8yUr8cKZ8u4eTyTJ+7T +ZTUiBqWZnSIPMMTTpZEsekkmQu+OSaG9XvSS9IyOyssRl+jb/DSh+W3EVdji9AmySRZ9fPJZ dVkSbPJIei7FvVm4yWmod0GCjVY3c+jGlLjKdlxQKMdHRrUIH7byrfuBUpqpYbZIbE5vPvXxr qIbhyc7/WTiHs2E9s+rdHf4QSG8V0qdyAzElwoaR1+p2Ulo+4dyS2CUxmLuoIiZmJ3fHreN4B A/qZgQzS1RkbY4isnZYk078znx02M2FRl0K+D3YeqiTmrhpp+oEMnP0uET1vHeWX5tM2OwCbz /RLJfzS Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 264 Lines: 9 > Although i don't know "out of memory" messages will be printed out by dmam_alloc_coherent() APIs > or not. Would such information belong to the programming interface documentation? Are there any related tags or source code annotations needed? Regards, Markus