From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Kiran Padwal <kiran.padwal@smartplayin.com>
Cc: support.opensource@diasemi.com,
anthony.olech.opensource@diasemi.com, david.chen@diasemi.com,
kiran.padwal21@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Input: da9055_onkey: Remove unnecessary OOM meassage
Date: Fri, 8 Aug 2014 09:26:54 -0700 [thread overview]
Message-ID: <20140808162654.GF26820@core.coreip.homeip.net> (raw)
In-Reply-To: <1407482097-17624-1-git-send-email-kiran.padwal@smartplayin.com>
On Fri, Aug 08, 2014 at 12:44:57PM +0530, Kiran Padwal wrote:
> There is no need to print out-of-memory errors since this is already
> done by the memory management subsystem which even calls dump_stack().
This is implementation detail as far as I am concerned. We might switch
dumping stack off down the road.
Thanks.
>
> Signed-off-by: Kiran Padwal <kiran.padwal@smartplayin.com>
> ---
> drivers/input/misc/da9055_onkey.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/input/misc/da9055_onkey.c b/drivers/input/misc/da9055_onkey.c
> index 4765799..ed6eaa9 100644
> --- a/drivers/input/misc/da9055_onkey.c
> +++ b/drivers/input/misc/da9055_onkey.c
> @@ -87,10 +87,8 @@ static int da9055_onkey_probe(struct platform_device *pdev)
> }
>
> onkey = devm_kzalloc(&pdev->dev, sizeof(*onkey), GFP_KERNEL);
> - if (!onkey) {
> - dev_err(&pdev->dev, "Failed to allocate memory\n");
> + if (!onkey)
> return -ENOMEM;
> - }
>
> input_dev = input_allocate_device();
> if (!input_dev) {
> --
> 1.7.9.5
>
--
Dmitry
prev parent reply other threads:[~2014-08-08 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 7:14 [PATCH 1/2] Input: da9055_onkey: Remove unnecessary OOM meassage Kiran Padwal
2014-08-08 16:26 ` Dmitry Torokhov [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=20140808162654.GF26820@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=anthony.olech.opensource@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=kiran.padwal21@gmail.com \
--cc=kiran.padwal@smartplayin.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=support.opensource@diasemi.com \
/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;
as well as URLs for NNTP newsgroup(s).