From: linux@rempel-privat.de (Oleksij Rempel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] initial suport for Alphascale ASM9260
Date: Tue, 28 Oct 2014 13:04:57 +0100 [thread overview]
Message-ID: <544F8669.2020807@rempel-privat.de> (raw)
In-Reply-To: <1414484787-6946-1-git-send-email-linux@rempel-privat.de>
Against which branch should be this code committable? There are some
merge conflicts against arm-soc/for-next branch.
Am 28.10.2014 um 09:26 schrieb Oleksij Rempel:
> This is reduced patchset to provide initial support for Alpascale ASM9260.
>
> Oleksij Rempel (2):
> ARM: add mach-asm9260
> ARM: add lolevel debug support for asm9260
>
> arch/arm/Kconfig | 2 ++
> arch/arm/Kconfig.debug | 33 ++++++++++++++++++++++++++++++---
> arch/arm/include/debug/asm9260.S | 31 +++++++++++++++++++++++++++++++
> arch/arm/mach-asm9260/Kconfig | 6 ++++++
> 4 files changed, 69 insertions(+), 3 deletions(-)
> create mode 100644 arch/arm/include/debug/asm9260.S
> create mode 100644 arch/arm/mach-asm9260/Kconfig
>
--
Regards,
Oleksij
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141028/8baa596e/attachment.sig>
next prev parent reply other threads:[~2014-10-28 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 8:26 [PATCH 0/2] initial suport for Alphascale ASM9260 Oleksij Rempel
2014-10-28 8:26 ` [PATCH 1/2 v2] ARM: add mach-asm9260 Oleksij Rempel
2014-10-28 8:26 ` [PATCH 2/2] ARM: add lolevel debug support for asm9260 Oleksij Rempel
2014-10-28 12:04 ` Oleksij Rempel [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-27 9:23 [PATCH 0/2] initial suport for Alphascale ASM9260 Oleksij Rempel
2014-11-17 8:27 ` Oleksij Rempel
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=544F8669.2020807@rempel-privat.de \
--to=linux@rempel-privat.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).