From: Nick Clifton <nickc@redhat.com>
To: Julian Brown <julian@codesourcery.com>
Cc: Paul Brook <paul@codesourcery.com>,
binutils@sources.redhat.com,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH] ARM Neon instruction set support
Date: Tue, 25 Apr 2006 19:12:00 -0000 [thread overview]
Message-ID: <444E5CE6.2040004@redhat.com> (raw)
In-Reply-To: <44464F50.1010108@codesourcery.com>
Hi Julian,
> If it's not bad form, I'd like to retract the "holding off on mainline
> submission" part of the above -- this patch is blocking some other
> patches on mainline, so I'd like to commit it now, if possible.
>
> If someone could review this
Very well, please consider your patch approved for the mainline as well.
But lets leave it out of the 2_17 branch, OK ?
Cheers
Nick
next prev parent reply other threads:[~2006-04-25 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 1:40 Julian Brown
2006-04-01 2:49 ` Paul Brook
2006-04-02 23:30 ` Julian Brown
2006-04-19 16:38 ` Julian Brown
2006-04-25 19:12 ` Nick Clifton [this message]
2006-04-25 19:20 ` [PATCH] ARM Neon programmers syntax Nick Clifton
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=444E5CE6.2040004@redhat.com \
--to=nickc@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sources.redhat.com \
--cc=julian@codesourcery.com \
--cc=paul@codesourcery.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).