linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Subject: [APPLIED] [PATCH v2 2/2] can:ti_hecc: Enable CAN support on AM3517.
Date: Tue, 4 May 2010 18:26:12 -0400	[thread overview]
Message-ID: <notify-1273011967@atomide.com> (raw)
In-Reply-To: <1267186035-8146-3-git-send-email-srk@ti.com>

This patch has been applied to the linux-omap
by youw fwiendly patch wobot.

Branch in linux-omap: for-next

Initial commit ID (Likely to change): 7241145120e803b600fc5aa1ef911c80ab68d1d5

PatchWorks
http://patchwork.kernel.org/patch/82312/

Git (Likely to change, and takes a while to get mirrored)
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=7241145120e803b600fc5aa1ef911c80ab68d1d5



  reply	other threads:[~2010-05-04 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 12:07 [PATCH v2 0/2] Enable CAN peripheral support on AM3517 Sriramakrishnan
2010-02-26 12:07 ` [PATCH v2 1/2] can:ti_hecc: board specific hookup on AM3517EVM Sriramakrishnan
2010-02-26 12:07   ` [PATCH v2 2/2] can:ti_hecc: Enable CAN support on AM3517 Sriramakrishnan
2010-05-04 22:26     ` Tony Lindgren [this message]
2010-04-01 14:11 ` [PATCH v2 0/2] Enable CAN peripheral " Govindarajan, Sriramakrishnan

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=notify-1273011967@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).