From: Greg KH <greg@kroah.com>
To: "Kilau, Scott" <Scott_Kilau@digi.com>
Cc: Greg.Chandler@wellsfargo.com, linux-kernel@vger.kernel.org
Subject: Re: kernel oops with extended serial stuff turned on...
Date: Wed, 18 Oct 2006 14:21:46 -0700 [thread overview]
Message-ID: <20061018212146.GA5206@kroah.com> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F803FDE@mtk-sms-mail01.digi.com>
On Wed, Oct 18, 2006 at 04:16:54PM -0500, Kilau, Scott wrote:
> Hi Greg C,
>
> > -----Original Message-----
> > From: Greg.Chandler@wellsfargo.com
> > [mailto:Greg.Chandler@wellsfargo.com]
> > Sent: Wednesday, October 18, 2006 4:07 PM
> > To: Kilau, Scott
> > Cc: linux-kernel@vger.kernel.org
> > Subject: RE: kernel oops with extended serial stuff turned on...
> >
> >
> > Should that be made a permanent patch then?
>
> In my out-of-tree drivers, yes, it was the correct way to fix
> the problem.
>
> I am probably not the best one to ask about the
> other serial drivers however...
>
> The "DEVFS" stuff was removed by Greg KH, I believe, so
> he probably is the best to decide upon the correct way of
> "fixing" it.
>
> Ie, I am not sure whether his intentions were to slide in a
> new patch on it later on to fix the problem with trying to
> register with sysfs/udev twice...
I don't understand, what problem is occuring here? Who is trying to
register with sysfs twice?
thanks,
greg k-h
next prev parent reply other threads:[~2006-10-18 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 21:16 kernel oops with extended serial stuff turned on Kilau, Scott
2006-10-18 21:21 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 22:35 Kilau, Scott
2006-10-18 23:09 ` Greg KH
2006-10-19 0:20 ` Kilau, Scott
2006-10-19 9:02 ` Jiri Slaby
2006-10-19 9:42 ` Jiri Slaby
2006-10-19 10:58 ` Kilau, Scott
2006-10-19 11:01 ` Jiri Slaby
2006-10-19 13:14 ` Alan Cox
2006-10-19 12:00 ` Alan Cox
2006-10-18 21:07 Greg.Chandler
2006-10-18 20:32 Kilau, Scott
2006-10-18 17:51 Greg.Chandler
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=20061018212146.GA5206@kroah.com \
--to=greg@kroah.com \
--cc=Greg.Chandler@wellsfargo.com \
--cc=Scott_Kilau@digi.com \
--cc=linux-kernel@vger.kernel.org \
/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