From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: [PATCH 0/3] Staging: xgifb: Removes dead code and unused spinlock conditional compilation logic
Date: Mon, 21 Feb 2011 09:09:04 +0000 [thread overview]
Message-ID: <1298279347-8825-1-git-send-email-martinez.javier@gmail.com> (raw)
In an earlier patch-set I was replacing a set of defines in staging xgifb driver
that hides the synchronization mechanism used to access critical sections.
As Dan Carpenter pointed me, this code depende on the accelerator engine being
activated (XGIfb_accel != 0), but in current driver this seems to be always
deactivated (XGIfb_accel = 0).
So this patchset removes all the unused code and this spinlock conditional
compilation logic only used in the acceleration mode code.
The patch-set is composed of the following patches:
[PATCH 1/3] Staging: xgifb: Removes dead code
[PATCH 2/3] Staging: xgifb: Remove unused functions
[PATCH 3/3] Staging: xgifb: Remove unused spinlock conditional compilation logic
next reply other threads:[~2011-02-21 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 9:09 Javier Martinez Canillas [this message]
2011-02-21 9:43 ` [PATCH 0/3] Staging: xgifb: Removes dead code and unused Dan Carpenter
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=1298279347-8825-1-git-send-email-martinez.javier@gmail.com \
--to=martinez.javier@gmail.com \
--cc=kernel-janitors@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