From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: Request for additional arm64 branch in linux-next
Date: Wed, 25 Mar 2015 18:42:44 +0100 [thread overview]
Message-ID: <20150325174244.GA3318@pd.tnic> (raw)
In-Reply-To: <20150325172002.GN24636@arm.com>
On Wed, Mar 25, 2015 at 05:20:03PM +0000, Will Deacon wrote:
> Hi Stephen,
>
> We've got a series of patches introducing ACPI support for arm64 that
Oh dear ARM comrades-in-arms, I was hearing rumours and was secretly
hoping that you would stay sane and not do the colossal mistake x86 did.
My condolences.
Perhaps not all is lost after all...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-03-25 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 17:20 Request for additional arm64 branch in linux-next Will Deacon
2015-03-25 17:42 ` Borislav Petkov [this message]
2015-03-26 0:10 ` Stephen Rothwell
2015-03-26 13:49 ` Will Deacon
2015-04-28 16:35 ` Will Deacon
2015-04-28 21:25 ` Stephen Rothwell
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=20150325174244.GA3318@pd.tnic \
--to=bp@alien8.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).