All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Michael Eager <eager@eagerm.com>
Subject: Re: [PATCH] arch/microblaze/include/asm/entry.h: Include "linux/linkage.h" to avoid compiling issue
Date: Mon, 01 Sep 2014 15:40:26 +0200	[thread overview]
Message-ID: <5404774A.3040501@monstr.eu> (raw)
In-Reply-To: <53F99CF3.8080905@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

Hi Chen,

On 08/24/2014 10:06 AM, Chen Gang wrote:
> Hello All:
> 
> Is microblaze for Linux upstream kernel still alive?
> 
> Before I get confirmation, I should do nothing for microblaze to avoid
> sending spams to kernel mailing list.

Yes. Microblaze is alive. I am just busy over summer in Europe.

I will reply the patch you sent.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-09-01 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 13:32 [PATCH] arch/microblaze/include/asm/entry.h: Include "linux/linkage.h" to avoid compiling issue Chen Gang
2014-08-19 15:47 ` Chen Gang
2014-08-24  8:06   ` Chen Gang
2014-09-01 13:40     ` Michal Simek [this message]
2014-09-01 15:30       ` Chen Gang
2014-09-01 14:01   ` Michal Simek
2014-09-01 13:59 ` Michal Simek

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=5404774A.3040501@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=eager@eagerm.com \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=linux-kernel@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.