public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Longnecker <mlongnecker@nvidia.com>
To: <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<mattias.nissler@gmx.de>
Subject: debugfs_create_{u,x,s}{8,16,32,64}
Date: Wed, 13 Aug 2014 14:57:05 -0700	[thread overview]
Message-ID: <53EBDF31.7010204@nvidia.com> (raw)

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? Would you entertain a similar patch 
today?

Thanks,
Matt Longnecker

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 21:57 Matt Longnecker [this message]
2014-08-13 21:57 ` debugfs_create_{u,x,s}{8,16,32,64} Greg KH
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=53EBDF31.7010204@nvidia.com \
    --to=mlongnecker@nvidia.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattias.nissler@gmx.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