From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Omar Ramirez Luna <omar.ramirez@copitl.com>
Cc: devel@driverdev.osuosl.org, Chen Gang <gang.chen@asianux.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: tidspbridge: for 3.9
Date: Thu, 17 Jan 2013 16:47:46 -0800 [thread overview]
Message-ID: <20130118004746.GA8897@kroah.com> (raw)
In-Reply-To: <1357810622-1709-1-git-send-email-omar.ramirez@copitl.com>
On Thu, Jan 10, 2013 at 03:36:57AM -0600, Omar Ramirez Luna wrote:
> Patches for staging-next, fixing comments and suggestions provided
> by Chen Gang.
>
> There is an additional scm patch, that removes hardcoded defines
> related to direct register handling for SCM, it was dependent on
> changes that already made it to mainline.
What is the status on getting this out of the staging tree? What needs
to be done still?
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-18 0:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 9:36 [PATCH 0/5] staging: tidspbridge: for 3.9 Omar Ramirez Luna
2013-01-10 9:36 ` [PATCH 1/5] staging: tidspbridge: fix potential array out of bounds write Omar Ramirez Luna
2013-01-10 9:36 ` [PATCH 2/5] staging: tidspbridge: fix memory corruption on long string names Omar Ramirez Luna
2013-01-10 9:37 ` [PATCH 3/5] staging: tidspbridge: fix uninitialized variable sym_name Omar Ramirez Luna
2013-01-10 9:37 ` [PATCH 4/5] staging: tidspbridge: use scm functions to set boot address and mode Omar Ramirez Luna
2013-01-10 9:37 ` [PATCH 5/5] staging: tidspbridge: remove unused code to handle iva_img Omar Ramirez Luna
2013-01-18 0:47 ` Greg Kroah-Hartman [this message]
2013-01-18 2:01 ` [PATCH 0/5] staging: tidspbridge: for 3.9 Tony Lindgren
2013-01-20 23:49 ` Omar Ramirez Luna
2013-01-20 23:45 ` Omar Ramirez Luna
2013-01-20 23:51 ` Greg Kroah-Hartman
2013-01-21 0:17 ` Omar Ramirez Luna
2013-01-21 7:25 ` Dan Carpenter
2013-01-21 9:49 ` Dan Carpenter
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=20130118004746.GA8897@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gang.chen@asianux.com \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@copitl.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.