All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-pwm@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] pwm: Drop unused #include <linux/radix-tree.h>
Date: Fri, 28 Jul 2023 09:30:13 +0200	[thread overview]
Message-ID: <ZMNuhcw1CIczzfxe@orome> (raw)
In-Reply-To: <20230728071259.590902-1-u.kleine-koenig@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

On Fri, Jul 28, 2023 at 09:12:59AM +0200, Uwe Kleine-König wrote:
> core.c doens't use any of the symbols provided by linux/radix-tree.h
> and compiles just fine without this include. So drop the #include.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
>  drivers/pwm/core.c | 1 -
>  1 file changed, 1 deletion(-)

Looks like I forgot to remove that when the radix tree support was
dropped in 247ee6c780406513c6031a7f4ea41f1648b03295. This didn't apply
cleanly, so it breaks the b4 tracking.

Applied, thanks.

Thierry

> 
> diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
> index 3dacceaef4a9..5b0794858ad4 100644
> --- a/drivers/pwm/core.c
> +++ b/drivers/pwm/core.c
> @@ -9,7 +9,6 @@
>  #include <linux/acpi.h>
>  #include <linux/module.h>
>  #include <linux/pwm.h>
> -#include <linux/radix-tree.h>
>  #include <linux/list.h>
>  #include <linux/mutex.h>
>  #include <linux/err.h>
> 
> base-commit: 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5
> -- 
> 2.39.2
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-07-28  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  7:12 [PATCH] pwm: Drop unused #include <linux/radix-tree.h> Uwe Kleine-König
2023-07-28  7:30 ` Thierry Reding [this message]
2023-07-28  7:59   ` Uwe Kleine-König

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=ZMNuhcw1CIczzfxe@orome \
    --to=thierry.reding@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-pwm@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.