From: Felipe Balbi <felipe.balbi@nokia.com>
To: "Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>
Cc: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
"tony@atomide.com" <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"h-kanigeri2@ti.com" <h-kanigeri2@ti.com>
Subject: Re: [GIT PULL] omap iommu: for-next for 2.6.35-rc1
Date: Wed, 2 Jun 2010 14:07:55 +0300 [thread overview]
Message-ID: <20100602110755.GL6465@nokia.com> (raw)
In-Reply-To: <20100602.140644.70200461.Hiroshi.DOYU@nokia.com>
On Wed, Jun 02, 2010 at 01:06:44PM +0200, Doyu Hiroshi (Nokia-D/Helsinki) wrote:
>This subject might be misleading.
>
>These patches are for for-next, which means for v2.6.36. "v2.6.35-rc1"
>on subject implies the base TAG for these patches.
ok, sorry for that :-)
--
balbi
DefectiveByDesign.org
next prev parent reply other threads:[~2010-06-02 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 7:50 [GIT PULL] omap iommu: for-next for 2.6.35-rc1 Hiroshi DOYU
2010-06-02 10:01 ` Felipe Balbi
2010-06-02 11:06 ` Hiroshi DOYU
2010-06-02 11:07 ` Felipe Balbi [this message]
2010-06-29 4:57 ` Hiroshi DOYU
2010-07-02 6:35 ` Hiroshi DOYU
2010-07-02 9:04 ` Tony Lindgren
2010-07-02 9:42 ` Hiroshi DOYU
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=20100602110755.GL6465@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=h-kanigeri2@ti.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.