mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "SL Baur" <steve@xemacs.org>
To: "Dan Williams" <dan.j.williams@intel.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
	kay.sievers@vrfy.org, neilb@suse.de, htejun@gmail.com,
	hpa@zytor.com, lkml@rtr.ca
Subject: Re: [PATCH] sysfs: add /sys/dev/{char, block} to lookup sysfs path by major:minor
Date: Mon, 14 Apr 2008 20:13:40 -0700	[thread overview]
Message-ID: <ed10ee420804142013ld540b76g200b459f13b34d@mail.gmail.com> (raw)
In-Reply-To: <20080414165036.13697.6532.stgit@dwillia2-linux.ch.intel.com>

On 4/14/08, Dan Williams <dan.j.williams@intel.com> wrote:

>  This is the second revision of the patch originally posted here:
>  http://marc.info/?l=linux-kernel&m=120795638915272&w=2
>
>  * Fixed up ENOMEM handling in devices_init()
>  * Added a short blurb in Documentation/filesystems/sysfs.txt
>
>   Documentation/filesystems/sysfs.txt |    6 +++++
>   drivers/base/core.c                 |   46 ++++++++++++++++++++++++++++++++++-
>   2 files changed, 51 insertions(+), 1 deletions(-)

I've looked this patch over and I have some comments.  The logic looks
correct, but there are two ugly lines.

>  @@ -775,6 +783,7 @@ int device_add(struct device *dev)
>         struct device *parent = NULL;
>         struct class_interface *class_intf;
>         int error;
>  +       char devt_str[25];

>  @@ -925,12 +944,16 @@ void device_del(struct device *dev)
>   {
>         struct device *parent = dev->parent;
>         struct class_interface *class_intf;
>  +       char devt_str[25];

May I ask why `25'?  The only other user of format_dev_t that I could find
in a quick grep is md (device-mapper) and they used a hardcoded `15' there.
The real problem is format_dev_t and print_dev_t.

If the only other user of those macros which want to be C inlines with
buffer size parameters is md, perhaps now would be a good time to clean
them up before adding more users?

Otherwise, the logic looks O.K.

Add my
Reviewed-by: SL Baur <steve@xemacs.org>
if that is appropriate.

-sb

  parent reply	other threads:[~2008-04-15  3:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 16:57 Dan Williams
2008-04-14 17:00 ` H. Peter Anvin
2008-04-15  3:13 ` SL Baur [this message]
2008-04-15  4:46   ` Dan Williams
2008-04-15  7:08     ` SL Baur

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=ed10ee420804142013ld540b76g200b459f13b34d@mail.gmail.com \
    --to=steve@xemacs.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 \
    /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

Powered by JetHome