public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sebastian Reichel <sre@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the gpio-intel tree
Date: Mon, 24 Feb 2025 12:02:01 +0200	[thread overview]
Message-ID: <Z7xDmddu6TZHNAFu@smile.fi.intel.com> (raw)
In-Reply-To: <20250224083406.6174f821@canb.auug.org.au>

On Mon, Feb 24, 2025 at 08:34:06AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Commits
> 
>   b16e9f8547a3 ("input: ipaq-micro-keys: use devm_kmemdup_array()")
>   67b12cda28e1 ("input: sparse-keymap: use devm_kmemdup_array()")
>   5f95e8d0be63 ("iio: adc: xilinx-xadc-core: use devm_kmemdup_array()")
>   18c4aec76056 ("pinctrl: pxa2xx: use devm_kmemdup_array()")
>   d7f6555aec79 ("pinctrl: tangier: use devm_kmemdup_array()")
>   6e1bba1140a9 ("pinctrl: cherryview: use devm_kmemdup_array()")
>   af946f612dfe ("pinctrl: baytrail: copy communities using devm_kmemdup_array()")
>   85ab35bae5ac ("pinctrl: intel: copy communities using devm_kmemdup_array()")
>   4c176c256dd9 ("devres: Introduce devm_kmemdup_array()")
>   d7a76a31c46e ("err.h: move IOMEM_ERR_PTR() to err.h")
> 
> are missing a Signed-off-by from their committer.

Thanks for the report!

But I dunno how to fix it now since it's most likely have been taken to some
other repos before battery.

I can issue another tag with that being addressed, nevertheless.

> Also, these have been merged into the battery tree.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-02-24 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-23 21:34 linux-next: Signed-off-by missing for commit in the gpio-intel tree Stephen Rothwell
2025-02-24 10:02 ` Andy Shevchenko [this message]
2025-02-24 10:30   ` Andy Shevchenko
2025-02-25  1:02     ` Sebastian Reichel

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=Z7xDmddu6TZHNAFu@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sre@kernel.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