From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Subject: [APPLIED] [PATCH v2 1/8] omap: 3630: update is_chip variable
Date: Tue, 10 Nov 2009 20:27:23 -0500 [thread overview]
Message-ID: <notify-1257902847@atomide.com> (raw)
In-Reply-To: <1257893249-15467-2-git-send-email-vikram.pandita@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): 4d2b130c190627af16cb7b9961da037436ad6d36
PatchWorks
http://patchwork.kernel.org/patch/59199/
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=4d2b130c190627af16cb7b9961da037436ad6d36
next prev parent reply other threads:[~2009-11-11 1:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 22:47 [PATCH v2 0/8] introduce 3630 boards Vikram Pandita
2009-11-10 22:47 ` [PATCH v2 1/8] omap: 3630: update is_chip variable Vikram Pandita
2009-11-10 22:47 ` [PATCH v2 2/8] omap: introduce OMAP_LL_DEBUG_NONE DEBUG_LL config Vikram Pandita
2009-11-10 22:47 ` [PATCH v2 3/8] omap: zoom2: split board file for software reuse Vikram Pandita
2009-11-10 22:47 ` [PATCH v2 4/8] omap: zoom2: update defconfig for LL_DEBUG_NONE Vikram Pandita
2009-11-10 22:47 ` [PATCH v2 5/8] omap: zoom3: introduce zoom3 board support Vikram Pandita
2009-11-10 22:47 ` [PATCH v2 6/8] omap: zoom3: defconfig creation Vikram Pandita
2009-11-10 22:47 ` [PATCH v2 7/8] omap: 3630sdp: introduce 3630 sdp board support Vikram Pandita
2009-11-10 22:47 ` [PATCH v2 8/8] omap: 3630sdp: defconfig creation Vikram Pandita
2009-11-11 1:24 ` [PATCH v2 3/8] omap: zoom2: split board file for software reuse Tony Lindgren
2009-11-11 1:32 ` [APPLIED] [PATCH v2 2/8] omap: introduce OMAP_LL_DEBUG_NONE DEBUG_LL config Tony Lindgren
2009-11-11 1:27 ` Tony Lindgren [this message]
2009-11-11 15:15 ` [PATCH v2 0/8] introduce 3630 boards Gadiyar, Anand
2009-11-11 15:19 ` Gadiyar, Anand
2009-11-11 15:28 ` Pandita, Vikram
2009-11-11 15:32 ` Gadiyar, Anand
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-1257902847@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 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.