From: Philippe De Muyter <phdm@macqel.be>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: linux-m68k@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [uClinux-dev] [PATCH] m68k: merge mmu and non-mmu bitops.h
Date: Thu, 19 May 2011 10:52:32 +0200 [thread overview]
Message-ID: <20110519085232.GA27058@frolo.macqel> (raw)
In-Reply-To: <1305696747-29641-1-git-send-email-gerg@snapgear.com>
On Wed, May 18, 2011 at 03:32:27PM +1000, gerg@snapgear.com wrote:
> From: Greg Ungerer <gerg@uclinux.org>
>
> The following patch merges the mmu and non-mmu versions of the m68k
> bitops.h files. Now there is a good deal of difference between the two
> files, but none of it is actually an mmu specific difference. It is
> all about the specific m68k/coldfire varient we are targeting. So it
> makes an awful lot of sense to merge these into a single bitops.h.
Thanks for taking care of that. Fork was easy (but ugly), but merge
is a tedious job.
Philippe
next prev parent reply other threads:[~2011-05-19 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 5:32 [PATCH] m68k: merge mmu and non-mmu bitops.h gerg
2011-05-19 8:52 ` Philippe De Muyter [this message]
2011-05-19 12:05 ` [uClinux-dev] " Greg Ungerer
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=20110519085232.GA27058@frolo.macqel \
--to=phdm@macqel.be \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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