From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v3 00/11] m68k: use asm-generic headers when possible
Date: Wed, 14 Nov 2012 20:29:33 +1000 [thread overview]
Message-ID: <50A3728D.9010209@snapgear.com> (raw)
In-Reply-To: <CAMuHMdVWaxjGYFXHwK6-CPUA3YFZ2x7k11FpPhMyudHt0xVa4g@mail.gmail.com>
Hi Geert,
On 11/14/2012 05:56 PM, Geert Uytterhoeven wrote:
> On Mon, Nov 12, 2012 at 5:19 AM, Greg Ungerer <gerg@snapgear.com> wrote:
>> On 11/11/12 20:30, Geert Uytterhoeven wrote:
>>> On Tue, Oct 30, 2012 at 7:24 AM, <gerg@snapgear.com> wrote:
>>>> Quite a few of the m68k asm headers are identical to the asm-generic
>>>> versions. So switch to using them where ever we can.
>>>>
>>>> v2 is rebased on top of 3.7-rc3.
>>>> v3 keep those in uapi/asm in uapi/asm (not moved to asm-generic)
>>>>
>>>> All defconfigs build. Run tested on ColdFire (with and without MMU) and
>>>> on
>>>> ArranyM.
>>>
>>>
>>> Thanks!
>>>
>>> Do you want me to queue these for 3.8, or take them yourselves?
>>> In the latter case:
>>> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
>>
>>
>> I don't really mind either way. Happy for you to take them
>> if that is your preference.
>>
>> Same goes for the mm/init.c changes too. Happy for you to
>> take them if you want.
>
> I applied all of them to master, and queued them in for-3.8/for-next, so they
> will be picked up by tomorrow's linux-next, which is the last one before
> next-20121126.
Thanks!
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2012-11-14 10:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 6:24 [PATCH v3 00/11] m68k: use asm-generic headers when possible gerg
2012-10-30 6:24 ` [PATCH v3 01/11] m68k: switch to using the asm-generic hw_irq.h gerg
2012-10-30 6:24 ` [PATCH v3 02/11] m68k: switch to using the asm-generic spinlock.h gerg
2012-10-30 6:24 ` [PATCH v3 03/11] m68k: switch to using the asm-generic shmparam.h gerg
2012-10-30 6:24 ` [PATCH v3 04/11] m68k: switch to using the asm-generic auxvec.h gerg
2012-10-30 6:24 ` [PATCH v3 05/11] m68k: switch to using the asm-generic msgbuf.h gerg
2012-10-30 6:24 ` [PATCH v3 06/11] m68k: switch to using the asm-generic sembuf.h gerg
2012-10-30 6:24 ` [PATCH v3 07/11] m68k: switch to using the asm-generic shmbuf.h gerg
2012-10-30 6:24 ` [PATCH v3 08/11] m68k: switch to using the asm-generic socket.h gerg
2012-10-30 6:24 ` [PATCH v3 09/11] m68k: switch to using the asm-generic sockios.h gerg
2012-10-30 6:24 ` [PATCH v3 10/11] m68k: switch to using the asm-generic termbits.h gerg
2012-10-30 6:24 ` [PATCH v3 11/11] m68k: switch to using the asm-generic termios.h gerg
2012-11-11 10:30 ` [PATCH v3 00/11] m68k: use asm-generic headers when possible Geert Uytterhoeven
2012-11-12 4:19 ` Greg Ungerer
2012-11-14 7:56 ` Geert Uytterhoeven
2012-11-14 10:29 ` Greg Ungerer [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=50A3728D.9010209@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-m68k@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.