From: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: viresh kumar
<viresh.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org"
<ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
spear-devel <spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org>,
"khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org"
<khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V2] i2c: designware: Add clk_{un}prepare() support
Date: Tue, 24 Apr 2012 09:01:11 +0530 [thread overview]
Message-ID: <4F961E7F.1020303@st.com> (raw)
In-Reply-To: <20120422183806.GB24810-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On 4/23/2012 12:08 AM, Wolfram Sang wrote:
> Okay, thanks, both applied to next. If you mention dependencies somewhere
> when submitting, that might speed things, a tiny bit at least.
I normally do this. But forgot it this time myself too, that this patch
had a dependency :(
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@st.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: viresh kumar <viresh.linux@gmail.com>,
"ben-linux@fluff.org" <ben-linux@fluff.org>,
spear-devel <spear-devel@list.st.com>,
"khali@linux-fr.org" <khali@linux-fr.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] i2c: designware: Add clk_{un}prepare() support
Date: Tue, 24 Apr 2012 09:01:11 +0530 [thread overview]
Message-ID: <4F961E7F.1020303@st.com> (raw)
In-Reply-To: <20120422183806.GB24810@pengutronix.de>
On 4/23/2012 12:08 AM, Wolfram Sang wrote:
> Okay, thanks, both applied to next. If you mention dependencies somewhere
> when submitting, that might speed things, a tiny bit at least.
I normally do this. But forgot it this time myself too, that this patch
had a dependency :(
--
viresh
next prev parent reply other threads:[~2012-04-24 3:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 8:53 [PATCH] i2c: designware: Add clk_{un}prepare() support Viresh Kumar
2012-04-17 8:53 ` Viresh Kumar
[not found] ` <caa4a0645f80f199b31ec16de37a5c4c9c67a6fa.1334652570.git.viresh.kumar-qxv4g6HH51o@public.gmane.org>
2012-04-17 11:34 ` [PATCH V2] " Viresh Kumar
2012-04-17 11:34 ` Viresh Kumar
2012-04-22 17:26 ` Wolfram Sang
2012-04-22 17:38 ` viresh kumar
[not found] ` <CAOh2x=mHS9h6kHxw2of-XWTtv35-SHRRno9Jdkb_3HuDoAovAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-22 18:38 ` Wolfram Sang
2012-04-22 18:38 ` Wolfram Sang
[not found] ` <20120422183806.GB24810-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-24 3:31 ` Viresh Kumar [this message]
2012-04-24 3:31 ` Viresh Kumar
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=4F961E7F.1020303@st.com \
--to=viresh.kumar-qxv4g6hh51o@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org \
--cc=viresh.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
/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.