public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: "Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
	linux-arm-kernel@lists.infradead.org, kevin@allwinnertech.com,
	sunny@allwinnertech.com, shuge@allwinnertech.com,
	linux-serial@vger.kernel.org,
	"Emilio López" <emilio@elopez.com.ar>,
	"Jiri Slaby" <jslaby@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: 8250_dw: add support for clk api
Date: Tue, 26 Mar 2013 16:34:33 -0700	[thread overview]
Message-ID: <20130326233433.GA31077@kroah.com> (raw)
In-Reply-To: <515179E6.4020709@free-electrons.com>

On Tue, Mar 26, 2013 at 11:35:18AM +0100, Maxime Ripard wrote:
> Hi Greg,
> 
> Le 21/03/2013 09:47, Heikki Krogerus a écrit :
> > On Tue, Mar 19, 2013 at 11:52:49AM +0100, Maxime Ripard wrote:
> >> From: Emilio López <emilio@elopez.com.ar>
> >>
> >> This commit implements support for using the clk api; this lets us use
> >> the "clocks" property with device tree, instead of having to use
> >> clock-frequency.
> >>
> >> Signed-off-by: Emilio López <emilio@elopez.com.ar>
> > 
> > FWIW,
> > 
> > Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> 
> Would you consider merging this patch, or do you have additional comments?
> 
> We have several patch series that depends on this one that I'd like to
> see included in 3.10, and we begin to see the end of the 3.9 release cycle.

You resent one patch, in the middle of a 7 patch series, with me on the
 cc: and somehow expected me to know that I was supposed to apply it?

Please be specific and realistic with your requests.

Resend it if you feel I should apply it.

greg k-h

  reply	other threads:[~2013-03-26 23:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1363689316-7847-1-git-send-email-maxime.ripard@free-electrons.com>
2013-03-19 10:35 ` [PATCH 1/7] serial: 8250_dw: add support for clk api Maxime Ripard
2013-03-19 10:50   ` Maxime Ripard
2013-03-19 10:52   ` [PATCH] " Maxime Ripard
2013-03-21  8:47     ` Heikki Krogerus
2013-03-26 10:35       ` Maxime Ripard
2013-03-26 23:34         ` Greg Kroah-Hartman [this message]
2013-03-19 10:35 ` [PATCH 2/7] ARM: sunxi: dt: Use clocks property instead of clock-frequency for the UARTs Maxime Ripard
2013-03-19 10:35 ` [PATCH 3/7] ARM: sunxi: Rename uart nodes to serial Maxime Ripard
2013-03-19 10:35 ` [PATCH 4/7] ARM: sunxi: dt: Move uart0 to sun4i-a10.dtsi Maxime Ripard
2013-03-19 10:35 ` [PATCH 5/7] ARM: sunxi: dt: Add uart3 dt node Maxime Ripard
2013-03-19 10:35 ` [PATCH 6/7] ARM: sunxi: dt: Add A10 UARTs to the dtsi Maxime Ripard
2013-03-19 10:35 ` [PATCH 7/7] ARM: sunxi: hackberry: Add UART muxing Maxime Ripard
2013-03-27 12:35 [PATCH] serial: 8250_dw: add support for clk api Maxime Ripard
2013-03-28 23:03 ` Greg Kroah-Hartman
2013-03-28 23:06   ` Maxime Ripard
2013-03-28 23:09     ` Greg Kroah-Hartman

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=20130326233433.GA31077@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=emilio@elopez.com.ar \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jslaby@suse.cz \
    --cc=kevin@allwinnertech.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=shuge@allwinnertech.com \
    --cc=sunny@allwinnertech.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