From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Fengguang Wu <wfg@linux.intel.com>
Cc: LKP <lkp@01.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [parport] BUG kmalloc-16 (Not tainted): Object already free
Date: Mon, 27 Jul 2015 10:34:58 +0530 [thread overview]
Message-ID: <20150727050458.GF3985@sudip-pc> (raw)
In-Reply-To: <20150726234659.GA12703@wfg-t540p.sh.intel.com>
On Mon, Jul 27, 2015 at 07:46:59AM +0800, Fengguang Wu wrote:
> Sorry for the duplicate report! It'll be auto avoided in future.
No problem. And thanks again for the script to reproduce the error. I am
still wondering why it did not came up in my tests before sending the
patch.
regards
sudip
prev parent reply other threads:[~2015-07-27 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 16:51 kernel test robot
2015-07-26 23:46 ` Fengguang Wu
2015-07-27 5:04 ` Sudip Mukherjee [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=20150727050458.GF3985@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=wfg@linux.intel.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
Powered by JetHome