From: Yani Ioannou <yani.ioannou@gmail.com>
To: Corey Minyard <minyard@acm.org>
Cc: Martin Drab <drab@kepler.fjfi.cvut.cz>,
openipmi-developer@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] IPMI: driver model and sysfs support
Date: Tue, 30 Aug 2005 14:13:13 -0400 [thread overview]
Message-ID: <25381867050830111345e27945@mail.gmail.com> (raw)
In-Reply-To: <43145D95.8060006@acm.org>
On 8/30/05, Corey Minyard <minyard@acm.org> wrote:
> This is very good. I believe the structure is correct, but I'm not a
> sysfs expert.
>
> There are a few things we need to deal with, though.
>
> * There are some significant changes to versioning in the
> driver that are in the mm tree right now (you can pull them from
>
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc6/2.6.13-rc6-mm2/broken-out)
Gah, ok :), I'll try to apply with the -mm changes.
> * There are some coding style problems. You have places like:
> +static void ipmi_bmc_unregister(struct ipmi_si_device *si,
> + struct ipmi_bmc_device *bmc){
> The '{' for functions and structures needs to be on it's own line.
> Also, several:
> + if(bmc->guid_present){
> that need spaces after the 'if' and before the '{'.
> The patch also adds some trailing spaces to empty lines, the
> following is a telltale sign:
> -
> +
> There was also one place where you added unneeded braces to
> a single statement and another where you deleted the empty line
> between two functions.
> These are all standard kernel coding style rules.
Yes, I should have caught those, thanks.
> * I'd prefer to store the product id, device id, and manufacturer id
> decoded. This makes it easier to handle (no need to use "memcmp"
> to compare) and print. The printing of the product id, for instance,
> will be rather unnatural in product_id_show().
I was under the impression that they were just OEM strings, and not
necessarily ASCII strings? I'll have a look at the specs again.
> * guids are not printable strings (see guid_show()).
guid_show, sounds useful!
Thanks,
Yani
next prev parent reply other threads:[~2005-08-30 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 10:56 [PATCH] IPMI: driver model and sysfs support Yani Ioannou
2005-08-30 13:22 ` Corey Minyard
2005-08-30 18:13 ` Yani Ioannou [this message]
2005-11-26 12:04 ` Yani Ioannou
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=25381867050830111345e27945@mail.gmail.com \
--to=yani.ioannou@gmail.com \
--cc=drab@kepler.fjfi.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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