mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] watchdog: wdat: fix mixed spaces/tabs in alignment
Date: Thu, 3 Mar 2022 11:06:19 +0100	[thread overview]
Message-ID: <20220303100619.GF19585@pengutronix.de> (raw)
In-Reply-To: <20220302200934.657994-1-ahmad@a3f.at>

On Wed, Mar 02, 2022 at 09:09:34PM +0100, Ahmad Fatoum wrote:
> Many struct members have a space followed by tabs for alignments. Drop
> the space.
> 
> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
> ---
>  drivers/watchdog/wdat_wdt.c | 36 ++++++++++++++++++------------------
>  1 file changed, 18 insertions(+), 18 deletions(-)

Applied, thanks

Sascha

> 
> diff --git a/drivers/watchdog/wdat_wdt.c b/drivers/watchdog/wdat_wdt.c
> index 39e8cc4a3dab..f58aee128301 100644
> --- a/drivers/watchdog/wdat_wdt.c
> +++ b/drivers/watchdog/wdat_wdt.c
> @@ -48,12 +48,12 @@ enum acpi_wdat_instructions {
>  /* WDAT Instruction Entries (actions) */
>  
>  struct __packed acpi_wdat_entry {
> -	u8 				action;
> -	u8 				instruction;
> -	u16 				reserved;
> -	struct acpi_generic_address 	register_region;
> -	u32 				value;		/* Value used with Read/Write register */
> -	u32 				mask;		/* Bitmask required for this register instruction */
> +	u8				action;
> +	u8				instruction;
> +	u16				reserved;
> +	struct acpi_generic_address	register_region;
> +	u32				value;		/* Value used with Read/Write register */
> +	u32				mask;		/* Bitmask required for this register instruction */
>  };
>  
>  /**
> @@ -82,7 +82,7 @@ struct wdat_instruction {
>  struct wdat_wdt {
>  	struct watchdog		wdd;
>  	unsigned int		period;
> -	bool 			stopped_in_sleep;
> +	bool			stopped_in_sleep;
>  	bool			stopped;
>  	struct list_head	*instructions[MAX_WDAT_ACTIONS];
>  };
> @@ -90,17 +90,17 @@ struct wdat_wdt {
>  struct __packed acpi_table_wdat {
>  	struct acpi_table_header header;	/* Common ACPI table header */
>  	u32			 header_length;	/* Watchdog Header Length */
> -	u16 			 pci_segment;	/* PCI Segment number */
> -	u8 			 pci_bus;	/* PCI Bus number */
> -	u8 			 pci_device;	/* PCI Device number */
> -	u8 			 pci_function;	/* PCI Function number */
> -	u8 			 reserved[3];
> -	u32 			 timer_period;	/* Period of one timer count (msec) */
> -	u32 			 max_count;	/* Maximum counter value supported */
> -	u32 			 min_count;	/* Minimum counter value */
> -	u8 			 flags;
> -	u8 			 reserved2[3];
> -	u32 			 nr_entries;	/* Number of watchdog entries that follow */
> +	u16			 pci_segment;	/* PCI Segment number */
> +	u8			 pci_bus;	/* PCI Bus number */
> +	u8			 pci_device;	/* PCI Device number */
> +	u8			 pci_function;	/* PCI Function number */
> +	u8			 reserved[3];
> +	u32			 timer_period;	/* Period of one timer count (msec) */
> +	u32			 max_count;	/* Maximum counter value supported */
> +	u32			 min_count;	/* Minimum counter value */
> +	u8			 flags;
> +	u8			 reserved2[3];
> +	u32			 nr_entries;	/* Number of watchdog entries that follow */
>  	struct acpi_wdat_entry   entries[];
>  };
>  
> -- 
> 2.34.1
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


      reply	other threads:[~2022-03-03 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 20:09 Ahmad Fatoum
2022-03-03 10:06 ` Sascha Hauer [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=20220303100619.GF19585@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=ahmad@a3f.at \
    --cc=barebox@lists.infradead.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