From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Russell King <linux@arm.linux.org.uk>,
Enric Balletbo i Serra <eballetbo@gmail.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: OMAP: Add maintainer entry for IGEP machines
Date: Tue, 6 Nov 2012 17:13:55 -0800 [thread overview]
Message-ID: <20121107011355.GY6801@atomide.com> (raw)
In-Reply-To: <1349686054-7486-1-git-send-email-javier@dowhile0.org>
* Javier Martinez Canillas <javier@dowhile0.org> [121008 01:49]:
> Enric and I have been mantained this machine and while we
> are moving to device trees, it is good that people cc us
> when reporting bugs or regression on the board file until
> we have proper DT support.
Thanks applying into omap-for-v3.8/board branch.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: OMAP: Add maintainer entry for IGEP machines
Date: Tue, 6 Nov 2012 17:13:55 -0800 [thread overview]
Message-ID: <20121107011355.GY6801@atomide.com> (raw)
In-Reply-To: <1349686054-7486-1-git-send-email-javier@dowhile0.org>
* Javier Martinez Canillas <javier@dowhile0.org> [121008 01:49]:
> Enric and I have been mantained this machine and while we
> are moving to device trees, it is good that people cc us
> when reporting bugs or regression on the board file until
> we have proper DT support.
Thanks applying into omap-for-v3.8/board branch.
Regards,
Tony
next prev parent reply other threads:[~2012-11-07 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 8:47 [PATCH 1/1] ARM: OMAP: Add maintainer entry for IGEP machines Javier Martinez Canillas
2012-10-08 8:47 ` Javier Martinez Canillas
2012-11-07 1:13 ` Tony Lindgren [this message]
2012-11-07 1:13 ` Tony Lindgren
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=20121107011355.GY6801@atomide.com \
--to=tony@atomide.com \
--cc=eballetbo@gmail.com \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.