From: Greg KH <greg@kroah.com>
To: Richard Retanubun <richardretanubun@ruggedcom.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Tang Nguyen <TangNguyen@ruggedcom.com>,
"m.grzeschik@pengutronix.de" <m.grzeschik@pengutronix.de>,
Arvid Brodin <Arvid.Brodin@xdin.com>,
linux-usb mailing list <linux-usb@vger.kernel.org>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>
Subject: Re: kmemleak report on isp1763 and sierra MC8705
Date: Mon, 29 Oct 2012 14:11:42 -0700 [thread overview]
Message-ID: <20121029211142.GA31351@kroah.com> (raw)
In-Reply-To: <508EEB48.9070508@ruggedcom.com>
On Mon, Oct 29, 2012 at 04:47:04PM -0400, Richard Retanubun wrote:
> On 26/10/12 07:35 PM, Greg KH wrote:
> >On Fri, Oct 26, 2012 at 05:57:23PM -0400, Richard Retanubun wrote:
> >>Hi Guys,
> >>
> >>I am debugging a reported kmemleak involving a sierra wireless MC8705 connected
> >>through isp1763 on powerpc linux-3.0.22
> >
> >Does this also happen on 3.6.3?
> >
> >thanks,
> >
> >greg k-h
>
> Hi Greg,
>
> Unfortunately, it is not trivial for us to update the kernel on this platform,
> Is there a specific experiment/patch I should look at for 3.0.22?
I have no idea, given that 3.0.22 is based on 18 month old kernel, tens
of thousands of patches ago.
You are on your own here, sorry.
Best of luck,
greg k-h
next prev parent reply other threads:[~2012-10-29 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 21:57 kmemleak report on isp1763 and sierra MC8705 Richard Retanubun
2012-10-26 23:35 ` Greg KH
2012-10-29 20:47 ` Richard Retanubun
2012-10-29 21:11 ` Greg KH [this message]
2012-10-29 22:14 ` Alan Stern
2012-11-09 22:14 ` Richard Retanubun
2012-11-10 14:30 ` Johan Hovold
2012-11-14 17:12 ` Richard Retanubun
2012-11-14 17:52 ` Johan Hovold
2012-11-21 1:15 ` Greg Kroah-Hartman
2012-11-25 14:24 ` Ben Hutchings
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=20121029211142.GA31351@kroah.com \
--to=greg@kroah.com \
--cc=Arvid.Brodin@xdin.com \
--cc=TangNguyen@ruggedcom.com \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=m.grzeschik@pengutronix.de \
--cc=richardretanubun@ruggedcom.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).