From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Aditya Pakki <pakki001@umn.edu>, Kangjie Lu <kjlu@umn.edu>,
kernel-janitors@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [v3] thunderbolt: Fix to check the return value of kmemdup
Date: Fri, 11 Oct 2019 17:42:16 +0300 [thread overview]
Message-ID: <20191011144216.GI2819@lahna.fi.intel.com> (raw)
In-Reply-To: <c12d7c9c-8212-ba9b-252f-7dbb61698550@web.de>
On Fri, Oct 11, 2019 at 04:13:22PM +0200, Markus Elfring wrote:
> Would you like to reconsider also the addition of the function call
> “tb_sw_warn(sw, "cannot allocate memory for switch\n")”?
For that I already have a patch as part of my USB4 support v2 series.
WARNING: multiple messages have this Message-ID (diff)
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Aditya Pakki <pakki001@umn.edu>, Kangjie Lu <kjlu@umn.edu>,
kernel-janitors@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [v3] thunderbolt: Fix to check the return value of kmemdup
Date: Fri, 11 Oct 2019 14:42:16 +0000 [thread overview]
Message-ID: <20191011144216.GI2819@lahna.fi.intel.com> (raw)
In-Reply-To: <c12d7c9c-8212-ba9b-252f-7dbb61698550@web.de>
On Fri, Oct 11, 2019 at 04:13:22PM +0200, Markus Elfring wrote:
> Would you like to reconsider also the addition of the function call
> “tb_sw_warn(sw, "cannot allocate memory for switch\n")”?
For that I already have a patch as part of my USB4 support v2 series.
next prev parent reply other threads:[~2019-10-11 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 21:25 [PATCH v3] thunderbolt: Fix to check the return value of kmemdup Aditya Pakki
2019-03-27 14:36 ` Mukesh Ojha
2019-03-28 8:35 ` Mika Westerberg
2019-10-11 13:00 ` [v3] " Markus Elfring
2019-10-11 13:00 ` Markus Elfring
2019-10-11 13:35 ` Mika Westerberg
2019-10-11 13:35 ` Mika Westerberg
2019-10-11 14:13 ` Markus Elfring
2019-10-11 14:13 ` Markus Elfring
2019-10-11 14:42 ` Mika Westerberg [this message]
2019-10-11 14:42 ` Mika Westerberg
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=20191011144216.GI2819@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Markus.Elfring@web.de \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=pakki001@umn.edu \
/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.