mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@misterjones.org>
To: "Amit Walambe" <amit.walambe@eurotech-ltd.co.uk>
Cc: <linux-kernel@vger.kernel.org>, "Greg KH" <greg@kroah.com>
Subject: Re: [PATCH][RFC][#2] Arcom Viper support for 2.6.26
Date: Mon, 14 Jul 2008 12:50:15 +0200	[thread overview]
Message-ID: <wrplk04pwns.fsf@hina.wild-wind.fr.eu.org> (raw)
In-Reply-To: <20080714112233.35577286@eurotech-ltd.co.uk> (Amit Walambe's message of "Mon, 14 Jul 2008 11:22:33 +0100")

>>>>> "Amit" == Amit Walambe <amit.walambe@eurotech-ltd.co.uk> writes:

Hi Amit,

Amit> Please note that Arcom is now part of Eurotech group and has changed
Amit> name to Eurotech (Ltd./Inc.). This is the updated link for the
Amit> product : http://www.eurotech.com/EN/products.aspx?pg=VIPER&pc=357

I'll make sure I'll use the updated link next time I mention the
board.

Amit> 2. If it is ok to merge the support but requires our review and
Amit> testing, I would try my best to put some time into it
Amit> ASAP. Though I must admit we might have bandwidth issues keeping
Amit> up with the mainline. But Marc, I assume, is stepping up for
Amit> this part.

I definitly am.

Even if the Viper board is old stuff these days, I think being able to
use a mainline kernel is a real bonus for people who already own this
system. Think about being able to use current distributions (I use
Debian/armel on mine).

Anyway, I'll be glad to assume the maintenance of this board, should a
version of this patch enter mainline.

Best regards,

	M.
-- 
And if you don't know where you're going, any road will take you there...

      reply	other threads:[~2008-07-14 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14  8:06 Marc Zyngier
2008-07-14 10:22 ` Amit Walambe
2008-07-14 10:50   ` Marc Zyngier [this message]

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=wrplk04pwns.fsf@hina.wild-wind.fr.eu.org \
    --to=maz@misterjones.org \
    --cc=amit.walambe@eurotech-ltd.co.uk \
    --cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®