From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject:
Date: Thu, 13 Jan 2011 19:14:53 -0600 [thread overview]
Message-ID: <1294967693-1938-1-git-send-email-omar.ramirez@ti.com> (raw)
Please pull these changes for 2.6.38:
The following changes since commit 3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5:
Linux 2.6.37 (2011-01-04 16:50:19 -0800)
are available in the git repository at:
git://dev.omapzoom.org/pub/scm/tidspbridge/kernel-dspbridge.git for-gkh-2.6.38
Guzman Lugo, Fernando (1):
staging: tidspbridge: configure full L1 MMU range
Omar Ramirez Luna (1):
staging: tidspbridge: replace mbox callback with notifier_call
drivers/staging/tidspbridge/core/tiomap3430.c | 15 +++++++--------
1 files changed, 7 insertions(+), 8 deletions(-)
Regards,
Omar
next reply other threads:[~2011-01-14 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 1:14 Omar Ramirez Luna [this message]
2011-01-14 4:36 ` your mail Greg KH
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=1294967693-1938-1-git-send-email-omar.ramirez@ti.com \
--to=omar.ramirez@ti.com \
--cc=devel@driverdev.osuosl.org \
--cc=felipe.contreras@gmail.com \
--cc=gregkh@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).