From: Michal Simek <michal.simek@xilinx.com>
To: Qiushi Wu <wu000273@umn.edu>, Michal Simek <michal.simek@xilinx.com>
Cc: David Laight <David.Laight@aculab.com>,
Wolfram Sang <wsa@kernel.org>, "kjlu@umn.edu" <kjlu@umn.edu>,
Rob Herring <robh@kernel.org>,
Shubhrajyoti Datta <shubhraj@xilinx.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: xiic: Fix reference count leaks.
Date: Mon, 27 Jul 2020 08:46:00 +0200 [thread overview]
Message-ID: <76c3abc8-12e1-5e58-7763-c6a46f87c12c@xilinx.com> (raw)
In-Reply-To: <CAMV6ehFtXcC-ba7RT95AC2bryh0E-9W1YYfkUBbZGDcLLL_6JA@mail.gmail.com>
Hi,
On 27. 07. 20 8:16, Qiushi Wu wrote:
> Hi Michal,
>
> Thanks for your reply!
> I checked the mailing list for the related emails against this API, but
> I didn't find any specific timeline they mentioned.
> Maybe we can patch this bug to prevent potential issues at this time
> point if you are willing to.
ok. I am fine with this but please send v2 and add there some comments
about it and extend commit message with more information you provided.
I just want to make sure that in several months timeframe when someone
look at this it will be clear that it was workaround.
Thanks,
Michal
prev parent reply other threads:[~2020-07-27 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 21:59 [PATCH] i2c: xiic: Fix reference count leaks wu000273
2020-06-14 9:09 ` Wolfram Sang
2020-06-17 14:30 ` David Laight
2020-07-13 7:54 ` Michal Simek
[not found] ` <CAMV6ehHR2+OSxj7rbWG_=ef2=aemecFk9u0yNSHN1keZZ3j5Bg@mail.gmail.com>
2020-07-21 6:02 ` Michal Simek
[not found] ` <CAMV6ehFtXcC-ba7RT95AC2bryh0E-9W1YYfkUBbZGDcLLL_6JA@mail.gmail.com>
2020-07-27 6:46 ` Michal Simek [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=76c3abc8-12e1-5e58-7763-c6a46f87c12c@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=David.Laight@aculab.com \
--cc=kjlu@umn.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shubhraj@xilinx.com \
--cc=wsa@kernel.org \
--cc=wu000273@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 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).