All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH] MAINTAINERS: Add Documentation/cpu-freq/
Date: Fri, 9 Sep 2016 13:08:19 +0200	[thread overview]
Message-ID: <20160909130819.3ae5dad5@endymion> (raw)
In-Reply-To: <20160909110603.GD18547@vireshk-i7>

On Fri, 9 Sep 2016 16:36:03 +0530, Viresh Kumar wrote:
> On 09-09-16, 13:05, Jean Delvare wrote:
> > I am told the cpufreq documentation updates should go to the PM list.
> > 
> > Signed-off-by: Jean Delvare <jdelvare@suse.de>
> > Reported-by: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
> > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> >  MAINTAINERS |    1 +
> >  1 file changed, 1 insertion(+)
> > 
> > --- linux-4.8-rc5.orig/MAINTAINERS	2016-09-09 13:00:13.928338065 +0200
> > +++ linux-4.8-rc5/MAINTAINERS	2016-09-09 13:00:51.102740802 +0200
> > @@ -3281,6 +3281,7 @@ L:	linux-pm@vger.kernel.org
> >  S:	Maintained
> >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> >  T:	git git://git.linaro.org/people/vireshk/linux.git (For ARM Updates)
> > +F:	Documentation/cpu-freq/
> >  F:	drivers/cpufreq/
> >  F:	include/linux/cpufreq.h
> 
> Oh, I missed that :(
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

No worry :) Thanks the quick ack.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2016-09-09 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 11:05 [PATCH] MAINTAINERS: Add Documentation/cpu-freq/ Jean Delvare
2016-09-09 11:06 ` Viresh Kumar
2016-09-09 11:08   ` Jean Delvare [this message]
2016-09-14  1:02     ` Rafael J. Wysocki

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=20160909130819.3ae5dad5@endymion \
    --to=jdelvare@suse.de \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=viresh.kumar@linaro.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.