All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Maksim Kiselev <bigunclemax@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/ledmon: new package
Date: Mon, 21 Aug 2023 13:11:59 +0200	[thread overview]
Message-ID: <20230821131159.46c0a6ff@windsurf> (raw)
In-Reply-To: <20230820095833.602364-2-bigunclemax@gmail.com>

Hello Maksim,

On Sun, 20 Aug 2023 12:58:33 +0300
Maksim Kiselev <bigunclemax@gmail.com> wrote:

> Enclosure LED Utilities
> 
> ledmon and ledctl are userspace tools designed to control storage
> enclosure LEDs. The user must have root privileges to use these tools.
> 
> These tools use the SGPIO and SES-2 protocols to monitor and control LEDs.
> They been verified to work with Intel(R) storage controllers (i.e. the
> Intel(R) AHCI controller) and have not been tested with storage controllers of
> other vendors (especially SAS/SCSI controllers).
> 
> For backplane enclosures attached to ISCI controllers, support is limited to
> Intel(R) Intelligent Backplanes.
> 
> Signed-off-by: Maksim Kiselev <bigunclemax@gmail.com>

Thanks, I've applied to our next branch, with some very small changes. See below.

> +Date: Mon, 15 May 2023 14:46:56 +0300
> +Subject: [PATCH 1/2] Replace nonstandard on_exit() function by atexit()
> +
> +Date: Mon, 15 May 2023 19:29:45 +0300
> +Subject: [PATCH 2/2] Fix unknown type name ‘ssize_t’ error

The patches in Buildroot should not have 1/2, 2/2, because this gets
quickly out of sync. And indeed: you have 3 patches for this package,
and these 1/2 and 2/2 are already wrong. So we ask people to generate
patches with "git format-patch -N". Note that you can run "make
check-package" which validates this kind of coding style issues.

> +LEDMON_VERSION = 0.97
> +LEDMON_SITE = $(call github,intel,ledmon,v$(LEDMON_VERSION))
> +LEDMON_DEPENDENCIES = host-pkgconf pciutils sg3_utils udev
> +LEDMON_LICENSE = GPL-2.0
> +LEDMON_LICENSE_FILES = COPYING
> +# The code base also include a COPYING.LIB file with the LGPL-2.1 text,
> +# and some source files are published under LGPL-2.1, but all of them are
> +# at some point linked with GPL-2.0 code, making the resulting binaries
> +# GPL-2.0 licensed

I've moved this comment above LEDMON_LICENSE, as we always put comments
*before* the code they correspond to.

> +LEDMON_AUTORECONF = YES

I've added a comment above this line that explains why it is needed.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-08-21 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20  9:58 [Buildroot] [PATCH v2 0/1] package/ledmon: new package Maksim Kiselev
2023-08-20  9:58 ` [Buildroot] [PATCH v2 1/1] " Maksim Kiselev
2023-08-21 11:11   ` Thomas Petazzoni via buildroot [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=20230821131159.46c0a6ff@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bigunclemax@gmail.com \
    --cc=thomas.petazzoni@bootlin.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.