Linux SPI subsystem development
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Lukas Bulwahn <lbulwahn@redhat.com>,
	Mark Brown <broonie@kernel.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Nuno Sa <nuno.sa@analog.com>,
	linux-spi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: adjust the file entry in SPI OFFLOAD
Date: Mon, 17 Feb 2025 09:31:39 -0600	[thread overview]
Message-ID: <7f0689d4-e940-4889-a29f-4fcbe8a32676@baylibre.com> (raw)
In-Reply-To: <20250217092851.17619-1-lukas.bulwahn@redhat.com>

On 2/17/25 3:28 AM, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> 
> Commit 8e02d1886988 ("spi: add basic support for SPI offloading") adds a
> new MAINTAINERS section referring to the non-existent file
> include/linux/spi/spi-offload.h rather than referring to the files added
> with this commit in the directory include/linux/spi/offload/.
> 
> Adjust the file reference to the intended directory.
> 
> Fixes: 8e02d1886988 ("spi: add basic support for SPI offloading")
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a54d8510ea6e..53cf3cbf33c9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -22402,7 +22402,7 @@ SPI OFFLOAD
>  R:	David Lechner <dlechner@baylibre.com>
>  F:	drivers/spi/spi-offload-trigger-pwm.c
>  F:	drivers/spi/spi-offload.c
> -F:	include/linux/spi/spi-offload.h
> +F:	include/linux/spi/offload/
>  K:	spi_offload
>  
>  SPI SUBSYSTEM

Thanks for fixing that.

Reviewed-by: David Lechner <dlechner@baylibre.com>


  reply	other threads:[~2025-02-17 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17  9:28 [PATCH] MAINTAINERS: adjust the file entry in SPI OFFLOAD Lukas Bulwahn
2025-02-17 15:31 ` David Lechner [this message]
2025-02-18 21:30 ` Mark Brown

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=7f0689d4-e940-4889-a29f-4fcbe8a32676@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=broonie@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lbulwahn@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=nuno.sa@analog.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