From: GregKH <greg@kroah.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Evgeniy Polyakov <zbr@ioremap.net>,
Fabio Estevam <fabio.estevam@freescale.com>,
s.hauer@pengutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] w1: mxc_w1: Adapt the clock name to the new clock framework
Date: Sun, 18 Nov 2012 18:18:30 -0800 [thread overview]
Message-ID: <20121119021830.GA29111@kroah.com> (raw)
In-Reply-To: <CAOMZO5C_uPVwNNhu+eUQCK9+J3xV5BNChf2nsjdNgEWRrQd4fA@mail.gmail.com>
On Sun, Nov 18, 2012 at 11:56:13PM -0200, Fabio Estevam wrote:
> Hi Sascha,
>
> On Wed, Oct 3, 2012 at 4:28 AM, Evgeniy Polyakov <zbr@ioremap.net> wrote:
> > On Tue, Oct 02, 2012 at 10:04:19PM -0300, Fabio Estevam (festevam@gmail.com) wrote:
> >> > I have no objections per se, but I'm hardly an expert in imx clock
> >> > framework :)
> >> >
> >> > Since it is only one patch in set of 3, I suppose it will be pushed
> >> > through different tree than w1. Feel free to add my ack.
> >> >
> >> > Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
> >>
> >> Could this series go via your tree?
> >
> > Please send it to Greg (added to CC), but I would like someone who knows
> > this platform (and not only w1 bits, which look good) to acknowledge changes,
> > feel free to add mine.
>
> Could you please ack this series?
>
> Greg,
>
> Should I re-send the patches with Evgeniy and Sascha's acks?
Please do so, so that I can apply them to my tree.
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-19 2:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 16:48 [PATCH v2 1/3] w1: mxc_w1: Adapt the clock name to the new clock framework Fabio Estevam
2012-10-01 17:51 ` Fabio Estevam
2012-10-02 5:32 ` Evgeniy Polyakov
2012-10-03 1:04 ` Fabio Estevam
2012-10-03 7:28 ` Evgeniy Polyakov
2012-11-19 1:56 ` Fabio Estevam
2012-11-19 2:18 ` GregKH [this message]
2012-10-03 10:11 ` Sascha Hauer
2012-11-19 10:07 ` Sascha Hauer
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=20121119021830.GA29111@kroah.com \
--to=greg@kroah.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=zbr@ioremap.net \
/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).