All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres-GANU6spQydw@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 1/3] subdev: add a pfuse subdev
Date: Mon, 25 Aug 2014 00:29:10 +0200	[thread overview]
Message-ID: <53FA6736.80000@free.fr> (raw)
In-Reply-To: <53FA66D3.8000703-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 25/08/2014 00:27, Christian Costa wrote:
> Hi Martin,
>
> I'm not very familiar with the function naming scheme but shouldn't 
> nouveau_fuse_rd32 use the same prefix as xxxx_fuse_ctor instead of 
> nouveau?
>
> Christian

Hey Christian,

You're right, I should have. It's not really a problem since the 
function is static. I'll send a v2 if Ben wants me to fix it :)

Martin

  parent reply	other threads:[~2014-08-24 22:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 21:15 [PATCH 1/3] subdev: add a pfuse subdev Martin Peres
     [not found] ` <1408914911-5022-1-git-send-email-martin.peres-GANU6spQydw@public.gmane.org>
2014-08-24 21:15   ` [PATCH 2/3] therm: make sure the temperature settings are sane on nv84+ Martin Peres
2014-08-24 21:15   ` [PATCH 3/3] therm/nv84+: do not expose non-calibrated internal temp sensor Martin Peres
     [not found]     ` <1408914911-5022-3-git-send-email-martin.peres-GANU6spQydw@public.gmane.org>
2014-08-27 22:53       ` Ben Skeggs
2014-08-24 22:27   ` [PATCH 1/3] subdev: add a pfuse subdev Christian Costa
     [not found]     ` <53FA66D3.8000703-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-08-24 22:29       ` Martin Peres [this message]
2014-08-24 23:35   ` Emil Velikov
     [not found]     ` <53FA76A7.4090803-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-08-25  0:07       ` Ben Skeggs
2014-08-25 22:26   ` [PATCH] subdev: add a pfuse subdev v2 Martin Peres

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=53FA6736.80000@free.fr \
    --to=martin.peres-ganu6spqydw@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.