Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	devel@driverdev.osuosl.org, linux-omap@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH v2] staging: tidspbridge: request dmtimer clocks on init
Date: Fri, 9 Dec 2011 14:38:44 -0800	[thread overview]
Message-ID: <20111209223844.GB25063@kroah.com> (raw)
In-Reply-To: <CAB-zwWg0FkNEHHVS=Hy-US9=xkueg_skUX7VCLS=QVN3ubTsTw@mail.gmail.com>

On Thu, Dec 08, 2011 at 07:44:28PM -0600, Ramirez Luna, Omar wrote:
> On Thu, Dec 8, 2011 at 6:07 PM, Greg KH <greg@kroah.com> wrote:
> >> > Definitely 3.2-fix material IMO :)
> >>
> >> I believe it was pushed to staging-next... I'm rooting so it can be
> >> pushed to staging-linus :)
> >
> > As it wasn't originally stated that this was a problem that needed to be
> > fixed for 3.2, can it wait for 3.3-rc1?  Especially given that there is
> > still discussion about this?
> 
> No discussion from me either.
> 
> The original intention was to include this patch for 3.2 because of
> the recent changes in dm timer framework, I apologize if "This was
> first seen on 3.2-rc1." is too ambiguous. I hope this can make it for
> 3.2 though.

How about for 3.2.1?  I'll try to get this into 3.2, but I can't
guarantee anything so late in the release cycle, sorry.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-12-09 22:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 22:18 [PATCH v2] staging: tidspbridge: request dmtimer clocks on init Omar Ramirez Luna
2011-12-07 22:11 ` Felipe Contreras
2011-12-08 19:10   ` Ramirez Luna, Omar
2011-12-08 19:50     ` Felipe Contreras
2011-12-08 20:14       ` Ramirez Luna, Omar
2011-12-08 20:11 ` Felipe Contreras
2011-12-08 20:16   ` Ramirez Luna, Omar
2011-12-09  0:07     ` Greg KH
2011-12-09  1:13       ` Felipe Contreras
2011-12-09  1:44       ` Ramirez Luna, Omar
2011-12-09 22:38         ` Greg KH [this message]
2011-12-10 11:55           ` Ramirez Luna, Omar

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=20111209223844.GB25063@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=felipe.contreras@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-omap@vger.kernel.org \
    --cc=omar.ramirez@ti.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