From: Greg KH <greg@kroah.com>
To: SL Baur <steve@xemacs.org>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
dan.j.williams@intel.com, akpm@linux-foundation.org,
hpa@zytor.com, htejun@gmail.com, kay.sievers@vrfy.org,
linux-kernel@vger.kernel.org, lkml@rtr.ca, neilb@suse.de
Subject: Re: patch sysfs-add-sys-dev-char-block-to-lookup-sysfs-path-by-major-minor.pat ch added to gregkh-2.6 tree
Date: Tue, 29 Apr 2008 08:22:49 -0700 [thread overview]
Message-ID: <20080429152249.GB11329@kroah.com> (raw)
In-Reply-To: <ed10ee420804290048pb0070ffhaf2e9dffe6868ac5@mail.gmail.com>
On Tue, Apr 29, 2008 at 12:48:11AM -0700, SL Baur wrote:
> On 4/28/08, gregkh@suse.de <gregkh@suse.de> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > Subject: sysfs: add /sys/dev/{char,block} to lookup sysfs path by major:minor
> >
> > to my gregkh-2.6 tree. Its filename is
> >
> > sysfs-add-sys-dev-char-block-to-lookup-sysfs-path-by-major-minor.patch
>
> > + char devt_str[15];
> > +
> > + if (kobj) {
> > + format_dev_t(devt_str, dev->devt);
>
> This part is ugly, but is not the fault of the patch. The ill-
> considered interface for `format_dev_t' is something that probably
> noone wants to fix.
Why not? Patches are always welcome, it's not like that function is
used in that many different places, should be a simple change...
> Otherwise, still OK with me.
>
> Reviewed-by: SL Baur <steve@xemacs.org>
>
> (Is Reviewed-by not sticky?)
Yes, it is, I'll add it to my version of the patch.
thanks,
greg k-h
prev parent reply other threads:[~2008-04-29 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1208800267.26479.3.camel@dwillia2-linux.ch.intel.com>
2008-04-28 23:51 ` patch sysfs-add-sys-dev-char-block-to-lookup-sysfs-path-by-major-minor.patch added to gregkh-2.6 tree gregkh
2008-04-29 7:48 ` SL Baur
2008-04-29 15:22 ` Greg KH [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=20080429152249.GB11329@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=htejun@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=neilb@suse.de \
--cc=steve@xemacs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox