linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mroberto@cpti.cetuc.puc-rio.br (Marcelo Jimenez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mach-sa1100: Put nanoEngine support back in the kernel.
Date: Tue, 9 Mar 2010 14:37:09 -0300	[thread overview]
Message-ID: <cecb6d8f1003090937t4ec3fe1cw293be3735caa2648@mail.gmail.com> (raw)
In-Reply-To: <20100309175229.c231f088.kristoffer.ericson@gmail.com>

Hi Kristoffer,

On Tue, Mar 9, 2010 at 13:52, Kristoffer Ericson
<kristoffer.ericson@gmail.com> wrote:
>
> Without testing it on the actual hardware it applies and looks good, compilation also goes smoothly without any issues.
> It looks quite alright to me. What are you planning to do with the fixup function?

Sorry, this function was the first things I wrote, but the kernel 2.6
infrastructure made it totally unnecessary and it should have been
removed. I will do it and send another patch.

> Im just missing the licensing text in the nano...c file for future reference,

Ok, I will add it too.

> after that feel free to add:
> Acked-by: Kristoffer Ericson <kristoffer.ericson@gmail.com>
>
> Best wishes
> Kristoffer

Regards,
Marcelo.

  reply	other threads:[~2010-03-09 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1268148843-13135-1-git-send-email-mroberto@cpti.cetuc.puc-rio.br>
2010-03-09 16:52 ` [PATCH] ARM: mach-sa1100: Put nanoEngine support back in the kernel Kristoffer Ericson
2010-03-09 17:37   ` Marcelo Jimenez [this message]
     [not found] <1268156514-1774-1-git-send-email-mroberto@cpti.cetuc.puc-rio.br>
2010-03-09 18:19 ` Kristoffer Ericson
2010-03-11 20:09 Marcelo Roberto Jimenez
2010-03-27 22:55 ` Russell King - ARM Linux
2010-03-29 19:10   ` Marcelo Jimenez
  -- strict thread matches above, loose matches on Subject: below --
2010-03-29 19:29 Marcelo Roberto Jimenez

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=cecb6d8f1003090937t4ec3fe1cw293be3735caa2648@mail.gmail.com \
    --to=mroberto@cpti.cetuc.puc-rio.br \
    --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).