From: Vaibhav Gupta <vaibhavgupta40@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Samuel Iglesias Gonsalvez <siglesias@igalia.com>,
Jens Taprogge <jens.taprogge@taprogge.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
industrypack-devel@lists.sourceforge.net,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] MAINTAINERS: ipack: add ipack.h header file
Date: Mon, 20 Oct 2025 11:14:00 +0000 [thread overview]
Message-ID: <aPYZeLtsXqNQYsce@gmail.com> (raw)
In-Reply-To: <20251014030038.759222-1-rdunlap@infradead.org>
On Mon, Oct 13, 2025 at 08:00:38PM -0700, Randy Dunlap wrote:
> Add the header file so that get_maintainer.pl will report useful
> info instead of just linux-kernel@vger.
>
> Fixes: 14dc124f1b2f ("MAINTAINERS: Add maintainers for Industry Pack subsystem")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
> Cc: Vaibhav Gupta <vaibhavgupta40@gmail.com>
> Cc: Jens Taprogge <jens.taprogge@taprogge.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: industrypack-devel@lists.sourceforge.net
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20251013.orig/MAINTAINERS
> +++ linux-next-20251013/MAINTAINERS
> @@ -12216,6 +12216,7 @@ L: industrypack-devel@lists.sourceforge.
> S: Maintained
> W: http://industrypack.sourceforge.net
> F: drivers/ipack/
> +F: include/linux/ipack.h
>
> INFINEON DPS310 Driver
> M: Eddie James <eajames@linux.ibm.com>
Hello Randy,
Thank you for your patch.
Acknowledged-by: Vaibhav Gupta <vaibhavgupta40@gmail.com>
Hey Greg, could you please add this patch to your misc tree?
Thanks,
Vaibhav
prev parent reply other threads:[~2025-10-20 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 3:00 [PATCH] MAINTAINERS: ipack: add ipack.h header file Randy Dunlap
2025-10-15 11:31 ` Vaibhav Gupta
2025-10-22 5:52 ` Greg Kroah-Hartman
2025-10-20 11:14 ` Vaibhav Gupta [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=aPYZeLtsXqNQYsce@gmail.com \
--to=vaibhavgupta40@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=industrypack-devel@lists.sourceforge.net \
--cc=jens.taprogge@taprogge.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=siglesias@igalia.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