From: Dan Carpenter <dan.carpenter@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Omar Ramirez Luna <omar.ramirez@copitl.com>,
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: Mon, 21 Jan 2013 10:25:24 +0300 [thread overview]
Message-ID: <20130121072524.GR4584@mwanda> (raw)
In-Reply-To: <20130118004746.GA8897@kroah.com>
On Thu, Jan 17, 2013 at 04:47:46PM -0800, Greg Kroah-Hartman wrote:
> 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?
>
Why can't tidspbridge be built as a module?
The Kconfig help files aren't very informative.
regards,
dan carpenter
next prev parent reply other threads:[~2013-01-21 7:25 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 ` [PATCH 0/5] staging: tidspbridge: for 3.9 Greg Kroah-Hartman
2013-01-18 2:01 ` 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 [this message]
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=20130121072524.GR4584@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gang.chen@asianux.com \
--cc=gregkh@linuxfoundation.org \
--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 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).