From: Greg KH <greg@kroah.com>
To: "Rachmel, Nir (Nir)" <rachmel@avaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops on hot insertion of USB
Date: Sat, 12 Apr 2008 09:59:19 -0700 [thread overview]
Message-ID: <20080412165919.GA30848@kroah.com> (raw)
In-Reply-To: <11486DD9B957EA488E21C44BC8737EFC55F379@307622ANEX5.global.avaya.com>
A: No.
Q: Should I include quotations after my reply?
On Sat, Apr 12, 2008 at 11:20:08AM +0200, Rachmel, Nir (Nir) wrote:
> Hi greg,
>
> Thanks for your reply. I am aware that I am "a bit" far behind in the
> Linux revsions tree,
Just a "bit", if you consider almost 3 years and many hundreds of
thousands of changes a "bit" :)
> however it will be very difficult for me to upgrade.
Why? Userspace should work just fine. If you are relying on custom
kernel modules, well, I think you now know the reason the kernel
developers are saying for people to get their code upstream to prevent
this kind of issue...
> I have done much work and testing with 2.6.14.7 and would
> prefer to patch it over upgrading it to the current version.
Hopefully you are able to patch all of the bugs and security issues that
have been found in the past 3 years.
> Was this problem fixed in a specific revision, or was the fix
> introduced due to several fixes in different areas? Maybe I can look
> at the specific fix and implement it on my own version.
All of our changes are public, I would suggest going through them and
trying to find it. Because you are relying on such an old, outdated,
and unsupported kernel version, you really are on your own.
good luck,
greg k-h
next prev parent reply other threads:[~2008-04-12 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 13:06 Kernel Oops on hot insertion of USB Rachmel, Nir (Nir)
2008-04-10 13:48 ` Bart Van Assche
2008-04-12 4:29 ` Greg KH
[not found] ` <11486DD9B957EA488E21C44BC8737EFC55F379@307622ANEX5.global.avaya.com>
2008-04-12 16:59 ` Greg KH [this message]
2008-04-12 19:08 ` Yinghai Lu
2008-04-12 19:47 ` Simon Holm Thøgersen
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=20080412165919.GA30848@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rachmel@avaya.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