From: Alexey Zaytsev <alexey.zaytsev@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
Trivial Kernel Patches <trivial@kernel.org>
Subject: [PATCH 0/5] [trivial] Fix dubious bitwise and/or usage.
Date: Sat, 10 Jan 2009 02:47:50 +0300 [thread overview]
Message-ID: <20090109234113.11800.55672.stgit@zaytsev.su> (raw)
Hello.
Sorry to bother the lkml with such trivial stuff, but
I could not get any response from either Jiri Kosina
ot trivial@ when I sent the patches directly to them.
Maybe a linux-trivial@ mailing list would be a good idea..
These patches fix a number of cases where &/| were by
mistake used instead of &&/||. In every single case the
semantics stays the same, so none is a real bug.
---
Alexey Zaytsev (5):
Fix dubious bitwise 'and' usage spotted by sparse.
Fix dubious bitwise 'and' usage spotted by sparse.
Fix dubious bitwise 'and' usage spotted by sparse.
Fix dubious bitwise 'or' usage spotted by sparse.
Fix dubious bitwise 'or' usage spotted by sparse.
drivers/isdn/mISDN/l1oip_codec.c | 2 +-
drivers/media/video/gspca/m5602/m5602_s5k4aa.c | 2 +-
drivers/net/wireless/ath9k/rc.c | 2 +-
drivers/usb/wusbcore/security.c | 2 +-
mm/page_alloc.c | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
--
next reply other threads:[~2009-01-09 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 23:47 Alexey Zaytsev [this message]
2009-01-09 23:47 ` [PATCH 1/5] Fix dubious bitwise 'or' usage spotted by sparse Alexey Zaytsev
2009-01-09 23:48 ` [PATCH 2/5] " Alexey Zaytsev
2009-01-09 23:48 ` [PATCH 3/5] Fix dubious bitwise 'and' " Alexey Zaytsev
2009-01-09 23:56 ` Jiri Kosina
2009-01-09 23:48 ` [PATCH 4/5] " Alexey Zaytsev
2009-01-09 23:58 ` Jiri Kosina
2009-01-09 23:48 ` [PATCH 5/5] " Alexey Zaytsev
2009-01-10 9:47 ` Tom Spink
2009-01-10 0:00 ` [PATCH 0/5] [trivial] Fix dubious bitwise and/or usage Jiri Kosina
2009-01-10 1:28 ` Alexey Zaytsev
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=20090109234113.11800.55672.stgit@zaytsev.su \
--to=alexey.zaytsev@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
all inboxes | Powered by JetHome®