From: Greg KH <greg@kroah.com>
To: ray-gmail@madrabbit.org
Cc: Adrian Bunk <bunk@stusta.de>,
Wolfgang Erig <Wolfgang.Erig@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: regression with gammu on 2.6.21-rc7
Date: Tue, 24 Apr 2007 20:39:07 -0700 [thread overview]
Message-ID: <20070425033907.GA10322@kroah.com> (raw)
In-Reply-To: <2c0942db0704241812m72e02611sc41f83c1b89629be@mail.gmail.com>
On Tue, Apr 24, 2007 at 06:12:33PM -0700, Ray Lee wrote:
> On 4/24/07, Greg KH <greg@kroah.com> wrote:
> > Also, if you know how to use git, doing a 'git bisect' to try to track
> > down the problem commit would be very helpful.
>
> Has to do with SIGIO, see this blog post:
>
> http://blog.cihar.com/archives/2007/04/24/kernel_2_6_21_hits_gammu/
Ah, thank you very much, that makes more sense as nothing changed in
that usb-serial driver and I was starting to get a bit worried...
thanks,
greg k-h
prev parent reply other threads:[~2007-04-25 3:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 8:58 regression with gammu on 2.6.21-rc7 Wolfgang Erig
2007-04-23 5:47 ` Greg KH
2007-04-23 8:10 ` Wolfgang Erig
2007-04-25 0:13 ` Greg KH
2007-04-25 1:12 ` Ray Lee
2007-04-25 3:39 ` Greg KH [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=20070425033907.GA10322@kroah.com \
--to=greg@kroah.com \
--cc=Wolfgang.Erig@gmx.de \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-gmail@madrabbit.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