From: Markus Elfring <Markus.Elfring@web.de>
To: Tomasz Figa <tomasz.figa@gmail.com>,
linux-clk@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
kernel-janitors@vger.kernel.org
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Aditya Pakki <pakki001@umn.edu>, Kangjie Lu <kjlu@umn.edu>,
Navid Emamdoost <emamd001@umn.edu>,
Stephen McCamant <smccaman@umn.edu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: clk: samsung: Checking a kmemdup() call in _samsung_clk_register_pll()
Date: Tue, 15 Oct 2019 17:55:18 +0000 [thread overview]
Message-ID: <cd91c7eb-7f14-e029-e495-6591987acf7c@web.de> (raw)
In-Reply-To: <CA+Ln22GpcMF5e8wjwoRH0wExyoGfta4n3YuaOBNDE+rfqhSZjg@mail.gmail.com>
> That said, there is no need to print any warnings or error messages on
> allocation failure, so technically they could be removed.
Do you find information sufficient from the Linux allocation failure report?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Tomasz Figa <tomasz.figa@gmail.com>,
linux-clk@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
kernel-janitors@vger.kernel.org
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Aditya Pakki <pakki001@umn.edu>, Kangjie Lu <kjlu@umn.edu>,
Navid Emamdoost <emamd001@umn.edu>,
Stephen McCamant <smccaman@umn.edu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: clk: samsung: Checking a kmemdup() call in _samsung_clk_register_pll()
Date: Tue, 15 Oct 2019 19:55:18 +0200 [thread overview]
Message-ID: <cd91c7eb-7f14-e029-e495-6591987acf7c@web.de> (raw)
In-Reply-To: <CA+Ln22GpcMF5e8wjwoRH0wExyoGfta4n3YuaOBNDE+rfqhSZjg@mail.gmail.com>
> That said, there is no need to print any warnings or error messages on
> allocation failure, so technically they could be removed.
Do you find information sufficient from the Linux allocation failure report?
Regards,
Markus
next prev parent reply other threads:[~2019-10-15 17:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191012141739epcas3p31e41c151b30d49c94aeb933aa42dc9f7@epcas3p3.samsung.com>
2019-10-12 14:17 ` clk: samsung: Checking a kmemdup() call in _samsung_clk_register_pll() Markus Elfring
2019-10-12 14:17 ` Markus Elfring
2019-10-12 14:17 ` Markus Elfring
2019-10-12 14:17 ` Markus Elfring
2019-10-15 14:49 ` Tomasz Figa
2019-10-15 14:49 ` Tomasz Figa
2019-10-15 17:55 ` Markus Elfring
2019-10-15 17:55 ` Markus Elfring
2019-10-16 11:43 ` Tomasz Figa
2019-10-16 11:43 ` Tomasz Figa
2019-10-16 11:58 ` Markus Elfring
2019-10-16 11:58 ` Markus Elfring
2019-10-15 17:55 ` Markus Elfring [this message]
2019-10-15 17:55 ` Markus Elfring
2019-10-16 10:55 ` Markus Elfring
2019-10-16 10:55 ` Markus Elfring
2019-10-16 11:44 ` Tomasz Figa
2019-10-16 11:44 ` Tomasz Figa
2019-10-14 6:55 ` Chanwoo Choi
2019-10-14 6:55 ` Chanwoo Choi
2019-10-14 8:05 ` Markus Elfring
2019-10-14 8:05 ` Markus Elfring
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=cd91c7eb-7f14-e029-e495-6591987acf7c@web.de \
--to=markus.elfring@web.de \
--cc=cw00.choi@samsung.com \
--cc=emamd001@umn.edu \
--cc=kernel-janitors@vger.kernel.org \
--cc=kjlu@umn.edu \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pakki001@umn.edu \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=smccaman@umn.edu \
--cc=tomasz.figa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.