public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@altera.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: Charles Manning <cdhmanning@gmail.com>,
	<linux-kernel@vger.kernel.org>, Chin Liang See <clsee@altera.com>
Subject: Re: [PATCH 0/3] clk : Fix SOCFPGA clk crash and some clean up
Date: Tue, 22 Jul 2014 10:34:05 -0500	[thread overview]
Message-ID: <1406043245.5571.4.camel@linux-builds1> (raw)
In-Reply-To: <738unmvspk.fsf@unicorn.hi.pengutronix.de>

Hi Charles,

On Tue, 2014-07-22 at 08:00 +0200, Steffen Trumtrar wrote:
> Hi!
> 
> As you touch clk.c, you should Cc
> 
>    Mike Turquette <mturquette@linaro.org>
> 
> He is the maintainer for that code.
> 

Yes, please use get_maintainer.pl on any files that you have a patch
for.

./scripts/get_maintainer.pl -f drivers/clk/socfpga/clk.c
Dinh Nguyen <dinguyen@altera.com> (maintainer:ARM/SOCFPGA CLOCK...)
Mike Turquette <mturquette@linaro.org> (maintainer:COMMON CLK FRAMEWORK)
linux-kernel@vger.kernel.org (open list:COMMON CLK FRAMEWORK)

Thanks,
Dinh
> Regards,
> Steffen
> 



      reply	other threads:[~2014-07-22 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  2:20 [PATCH 0/3] clk : Fix SOCFPGA clk crash and some clean up Charles Manning
2014-07-22  2:20 ` [PATCH 1/3] clk : Clean up checkpatch warnings Charles Manning
2014-07-30 12:19   ` Pavel Machek
2014-07-22  2:20 ` [PATCH 2/3] clk: Prevent a hanging pointer being abused Charles Manning
2014-07-30 12:20   ` Pavel Machek
2014-07-22  2:20 ` [PATCH 3/3] clk: socfpga Change name look-up to not use the init pointer Charles Manning
2014-07-22  6:00 ` [PATCH 0/3] clk : Fix SOCFPGA clk crash and some clean up Steffen Trumtrar
2014-07-22 15:34   ` Dinh Nguyen [this message]

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=1406043245.5571.4.camel@linux-builds1 \
    --to=dinguyen@altera.com \
    --cc=cdhmanning@gmail.com \
    --cc=clsee@altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.trumtrar@pengutronix.de \
    /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