All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Matt Longnecker <mlongnecker@nvidia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	mattias.nissler@gmx.de
Subject: Re: debugfs_create_{u,x,s}{8,16,32,64}
Date: Thu, 14 Aug 2014 05:57:42 +0800	[thread overview]
Message-ID: <20140813215742.GA7908@kroah.com> (raw)
In-Reply-To: <53EBDF31.7010204@nvidia.com>

On Wed, Aug 13, 2014 at 02:57:05PM -0700, Matt Longnecker wrote:
> Greg,
> 
> Back in December 2007 Mattias Nissler proposed a patch defining
> debugfs_create_s32 and friends. In it he reworked the already existent u and
> x versions. The subject of Mattias's mail was "[PATCH] debugfs: Revamp
> debugfs_create_{u,x,s}{8,16,32,64} to support signed integers".
> 
> As I'm writing a new driver related to thermal management, I'm finding the
> absence of debugfs_create_s32 to be a stumbling block. I see at least two
> other folks who have stumbled on the absence of debugfs_create_s32 in the
> past few years.
> 
> Why didn't we merge Mattias's patch?

I can't remember why I didn't merge a patch from last week, let alone
from 2007, are you crazy?  :)

> Would you entertain a similar patch today?

I always entertain all patches, you never need to ask if you are allowed
to send a patch, that's like asking "Am I allowed to ask a question?"...

greg k-h

  reply	other threads:[~2014-08-13 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 21:57 debugfs_create_{u,x,s}{8,16,32,64} Matt Longnecker
2014-08-13 21:57 ` Greg KH [this message]
2014-08-14  9:33   ` debugfs_create_{u,x,s}{8,16,32,64} Mattias Nissler

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=20140813215742.GA7908@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattias.nissler@gmx.de \
    --cc=mlongnecker@nvidia.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.