From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Newest kernel appears to break tap feature - good starting point for kernel development?
Date: Sat, 4 Feb 2012 14:03:05 +0700 [thread overview]
Message-ID: <CAGdaadZ41g4HutXqWn8FRdxjBiC0X6xaB9XgfkQNTHHzFOea0A@mail.gmail.com> (raw)
In-Reply-To: <4F2C5B89.8060900@mage.me.uk>
Hi Reza....
On Sat, Feb 4, 2012 at 05:11, Reza <vivi@mage.me.uk> wrote:
> Hi all,
>
> I'm interested in getting involved in kernel development. I compiled the
> latest kernel and found that it broke the tap feature on my asus x54h
> k54l. I had a look at the way the devices were interpreted and
> /proc/bus/input/devices gave different results. This seems like it may
> be a good starting point but I'm not sure where to go from here or
> whether it's an issue with the kernel. I presume it is as switching back
> to the older kernel fixes the tapping for left click.
Likely you found regression here.
I think the key here is by using git feature called "bisect" to find
out the culprit. This might require repetitive kernel build and re
test. It's kinda trial work, only here you got help from git as the
revision control.
Once you found the commit that introduce the bug, you can either
remove that (of course, without introducing instability) or improve
it.
It all might sound easy, but require patience and time.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2012-02-04 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 22:11 Newest kernel appears to break tap feature - good starting point for kernel development? Reza
2012-02-04 7:03 ` Mulyadi Santosa [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=CAGdaadZ41g4HutXqWn8FRdxjBiC0X6xaB9XgfkQNTHHzFOea0A@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).