From: Andreas Schwab <schwab@linux-m68k.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Mikael Pettersson <mikpe@it.uu.se>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsprogs: m68k bitops fixes
Date: Mon, 17 Dec 2012 19:15:30 +0100 [thread overview]
Message-ID: <m2a9tc7dfh.fsf@igel.home> (raw)
In-Reply-To: <20121217144902.GC31563@thunk.org> (Theodore Ts'o's message of "Mon, 17 Dec 2012 09:49:02 -0500")
Theodore Ts'o <tytso@mit.edu> writes:
> It would be a good idea to check the m68k kernel, since it was cribbed
> from the kernel sources.
The kernel bitops always use signed bit numbers.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2012-12-17 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 13:40 [PATCH] e2fsprogs: m68k bitops fixes Mikael Pettersson
2012-12-16 21:39 ` Mikael Pettersson
2012-12-17 14:49 ` Theodore Ts'o
2012-12-17 18:15 ` Andreas Schwab [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=m2a9tc7dfh.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linux-ext4@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=tytso@mit.edu \
/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).