From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: M68k tree updates
Date: Sun, 06 Dec 2009 22:25:58 +0300 [thread overview]
Message-ID: <4B1C0546.5040205@codesourcery.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0911252213340.31650@ayla.of.borg>
Geert Uytterhoeven wrote:
> It took me a while, but finally I managed to update
> http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git again.
>
> I added the following to master (the main development branch):
...
> I haven't updated m68k-queue (the branch with clean m68k changes w.r.t.
> Linus' tree) yet.
>
> If anything is missing, please tell me. Thx!
I almost forgot about these two patches:
0001-Define-sigcontext-ABI-of-ColdFire.patch
0002-Fix-m68k-uclinux-s-rt_sigreturn-trampoline.patch
The first patch makes `struct sigcontext' compatible with ColdFire and
fixes the rt_sigreturn trampoline for ColdFire. The second patch fixes
a typo in m68knommu code for rt_sigreturn trampoline.
Both patches are attached to this message
http://marc.info/?l=linux-m68k&m=125365546306821&w=2 .
I'll appreciate merging these patches to master if it's not too late.
Thanks,
--
Maxim Kuvyrkov
CodeSourcery
maxim@codesourcery.com
(650) 331-3385 x724
prev parent reply other threads:[~2009-12-06 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 21:20 M68k tree updates Geert Uytterhoeven
2009-11-30 13:43 ` Maxim Kuvyrkov
2009-12-04 19:57 ` Geert Uytterhoeven
2009-12-05 18:53 ` Maxim Kuvyrkov
2009-12-07 6:42 ` Greg Ungerer
2009-12-06 19:25 ` Maxim Kuvyrkov [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=4B1C0546.5040205@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox