From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nishanth Menon <nm@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
linux-pm <linux-pm@lists.linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
l-o <linux-omap@vger.kernel.org>,
l-a <linux-arm-kernel@lists.infradead.org>,
Paul <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH v7] power: introduce library for device-specific OPPs
Date: Tue, 12 Oct 2010 00:08:16 +0200 [thread overview]
Message-ID: <201010120008.16388.rjw@sisk.pl> (raw)
In-Reply-To: <4CB32675.1090205@ti.com>
On Monday, October 11, 2010, Nishanth Menon wrote:
> Rafael J. Wysocki had written, on 10/09/2010 05:59 PM, the following:
> [...]
> >>
> >> Signed-off-by: Nishanth Menon <nm@ti.com>
> >
> > OK
> >
> > Your error messages are a bit inconsistent (e.g. some of them print the
> > error code while others don't), but I guess I can fix that up.
> Thanks a bunch.
> >
> > Still, to apply the patch I need a copyright notice for the doc too.
> oops..
> (C) 2009-2010 Nishanth Menon <nm@ti.com>, Texas Instruments Incorporated
> Does this help?
Yes, it does.
> or would you like me to post a v8 as well?
That shouldn't be necessary.
Thanks,
Rafael
WARNING: multiple messages have this Message-ID (diff)
From: rjw@sisk.pl (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7] power: introduce library for device-specific OPPs
Date: Tue, 12 Oct 2010 00:08:16 +0200 [thread overview]
Message-ID: <201010120008.16388.rjw@sisk.pl> (raw)
In-Reply-To: <4CB32675.1090205@ti.com>
On Monday, October 11, 2010, Nishanth Menon wrote:
> Rafael J. Wysocki had written, on 10/09/2010 05:59 PM, the following:
> [...]
> >>
> >> Signed-off-by: Nishanth Menon <nm@ti.com>
> >
> > OK
> >
> > Your error messages are a bit inconsistent (e.g. some of them print the
> > error code while others don't), but I guess I can fix that up.
> Thanks a bunch.
> >
> > Still, to apply the patch I need a copyright notice for the doc too.
> oops..
> (C) 2009-2010 Nishanth Menon <nm@ti.com>, Texas Instruments Incorporated
> Does this help?
Yes, it does.
> or would you like me to post a v8 as well?
That shouldn't be necessary.
Thanks,
Rafael
next prev parent reply other threads:[~2010-10-11 22:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH] power: introduce library for device-specific OPPs>
2010-10-08 3:02 ` [PATCH v7] power: introduce library for device-specific OPPs Nishanth Menon
2010-10-08 3:02 ` Nishanth Menon
2010-10-09 22:59 ` Rafael J. Wysocki
2010-10-09 22:59 ` Rafael J. Wysocki
2010-10-09 22:59 ` Rafael J. Wysocki
2010-10-11 14:43 ` Kevin Hilman
2010-10-11 14:43 ` Kevin Hilman
2010-10-11 14:43 ` Kevin Hilman
2010-10-11 15:00 ` Nishanth Menon
2010-10-11 15:00 ` Nishanth Menon
2010-10-11 15:00 ` Nishanth Menon
2010-10-11 22:08 ` Rafael J. Wysocki [this message]
2010-10-11 22:08 ` Rafael J. Wysocki
2010-10-12 23:25 ` Rafael J. Wysocki
2010-10-12 23:25 ` Rafael J. Wysocki
2010-10-12 23:25 ` Rafael J. Wysocki
2010-10-12 23:57 ` Nishanth Menon
2010-10-12 23:57 ` Nishanth Menon
2010-10-12 23:57 ` Nishanth Menon
2010-10-11 22:08 ` Rafael J. Wysocki
2010-10-08 3:02 ` Nishanth Menon
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=201010120008.16388.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nm@ti.com \
--cc=paulmck@linux.vnet.ibm.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 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.