Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Marco Scardovi <mscardovi95@gmail.com>
Cc: mika.westerberg@intel.com, mathias.nyman@intel.com,
	linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] gpio: acpi: modernize resource management using cleanup.h
Date: Thu, 7 May 2026 22:19:13 +0300	[thread overview]
Message-ID: <afzlsRkyKQzuUcgL@ashevche-desk.local> (raw)
In-Reply-To: <20260507155647.403964-1-mscardovi95@gmail.com>

On Thu, May 07, 2026 at 05:56:41PM +0200, Marco Scardovi wrote:
> Hi Andy, Mika,
> thanks for the patience: I was way too excited about my first patch on
> the linux kernel and let it takes over the reasoning and I'm sorry for that.
> I've moved the defines on the right places as requested and refactored the
> patches to be smaller and tested the build with KASAN and kmemleak as requested
> by @Mika without any visible regression as for now.

You MUST provide:
- DCO (Developer certificate of origin)
- commit messages

Without that, it's no go *at all*.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2026-05-07 19:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260506123421.1077421-1-mscardovi95@gmail.com>
2026-05-07 15:56 ` [PATCH v3 0/6] gpio: acpi: modernize resource management using cleanup.h Marco Scardovi
2026-05-07 15:56   ` [PATCH v3 1/6] ACPI: Move DEFINE_FREE(acpi_free) to global header Marco Scardovi
2026-05-07 15:56   ` [PATCH v3 2/6] gpiolib: Move DEFINE_FREE(free_gpio_desc) to driver header Marco Scardovi
2026-05-07 15:56   ` [PATCH v3 3/6] gpio: acpi: ignore out-of-range pins in acpi_gpiochip_alloc_event() Marco Scardovi
2026-05-07 15:56   ` [PATCH v3 4/6] gpio: acpi: use guard(mutex) for conn_lock Marco Scardovi
2026-05-07 15:56   ` [PATCH v3 5/6] gpio: acpi: use cleanup.h for automated resource deallocation Marco Scardovi
2026-05-07 15:56   ` [PATCH v3 6/6] gpio: acpi: sort header inclusion alphabetically Marco Scardovi
2026-05-07 19:19   ` Andy Shevchenko [this message]
2026-05-08  6:17     ` [PATCH v4 0/6] gpio: acpi: modernize resource management using cleanup.h Marco Scardovi
2026-05-08  6:17       ` [PATCH v4 1/6] ACPI: Move DEFINE_FREE(acpi_free) to global header Marco Scardovi
2026-05-08 18:40         ` Rafael J. Wysocki
2026-05-08  6:17       ` [PATCH v4 2/6] gpiolib: Move DEFINE_FREE(free_gpio_desc) to driver header Marco Scardovi
2026-05-08  6:17       ` [PATCH v4 3/6] gpio: acpi: ignore out-of-range pins in acpi_gpiochip_alloc_event() Marco Scardovi
2026-05-08  6:17       ` [PATCH v4 4/6] gpio: acpi: use guard(mutex) for conn_lock Marco Scardovi
2026-05-08  6:17       ` [PATCH v4 5/6] gpio: acpi: use cleanup.h for automated resource deallocation Marco Scardovi
2026-05-08 18:44         ` Rafael J. Wysocki
2026-05-08  6:17       ` [PATCH v4 6/6] gpio: acpi: sort header inclusion alphabetically Marco Scardovi
2026-05-08  7:21       ` [PATCH v4 0/6] gpio: acpi: modernize resource management using cleanup.h Andy Shevchenko
2026-05-08  7:22         ` Andy Shevchenko

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=afzlsRkyKQzuUcgL@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=mika.westerberg@intel.com \
    --cc=mscardovi95@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox