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: Wed, 16 Oct 2019 13:58:04 +0200 [thread overview]
Message-ID: <43617d6a-c778-629b-81b0-aa0accf09d80@web.de> (raw)
In-Reply-To: <CA+Ln22FCH-q-joG6i=K2u=3vZTwwytkk0Q48oKekGkVb+VtL3Q@mail.gmail.com>
> A backtrace should be enough for this kind of a failure that shouldn't
> normally happen and if happens, then the rest of the system must be in
> a state already about to fail anyway.
Does this feedback mean that you would like to omit two extra
error messages from this function implementation?
Regards,
Markus
next prev parent reply other threads:[~2019-10-16 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 14:17 clk: samsung: Checking a kmemdup() call in _samsung_clk_register_pll() Markus Elfring
2019-10-15 14:49 ` Tomasz Figa
2019-10-15 17:55 ` Markus Elfring
2019-10-16 11:43 ` Tomasz Figa
2019-10-16 11:58 ` Markus Elfring [this message]
2019-10-15 17:55 ` Markus Elfring
2019-10-16 10:55 ` Markus Elfring
2019-10-16 11:44 ` Tomasz Figa
[not found] <CGME20191012141739epcas3p31e41c151b30d49c94aeb933aa42dc9f7@epcas3p3.samsung.com>
2019-10-12 14:17 ` Markus Elfring
2019-10-14 6:55 ` Chanwoo Choi
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=43617d6a-c778-629b-81b0-aa0accf09d80@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 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).