The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michail Tatas <michail.tatas@gmail.com>
To: dpenkler@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Drivers: gpib: Fix Typos
Date: Thu, 21 May 2026 01:57:51 +0300	[thread overview]
Message-ID: <ag48b4hk80YzeTwz@michalis-linux> (raw)
In-Reply-To: <aTs1U2i_RObUspXH@michalis-linux>

On Thu, Dec 11, 2025 at 11:19:15PM +0200, Michail Tatas wrote:
> Corrected minor typos in drivers/gpib/eastwood/fluke_gpib.c
> according to instructions in the TODO file
> 
> Signed-off-by: Michail Tatas <michail.tatas@gmail.com>
> ---
>  drivers/gpib/eastwood/fluke_gpib.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpib/eastwood/fluke_gpib.c b/drivers/gpib/eastwood/fluke_gpib.c
> index 3ae848e3f738..a390bb798f25 100644
> --- a/drivers/gpib/eastwood/fluke_gpib.c
> +++ b/drivers/gpib/eastwood/fluke_gpib.c
> @@ -1,7 +1,7 @@
>  // SPDX-License-Identifier: GPL-2.0
>  
>  /***************************************************************************
> - * GPIB Driver for Fluke cda devices.  Basically, its a driver for a (bugfixed)
> + * GPIB Driver for Fluke cda devices.  Basically, it's a driver for a (bugfixed)
>   * cb7210 connected to channel 0 of a pl330 dma controller.
>   *    Author: Frank Mori Hess <fmh6jj@gmail.com>
>   *   copyright: (C) 2006, 2010, 2015 Fluke Corporation
> @@ -286,7 +286,7 @@ static int wait_for_read(struct gpib_board *board)
>   * in the case where the handshake is stuck in SGNS due to no byte being
>   * available to the chip (and thus we can be confident a dma transfer will
>   * result in at least one byte making it into the chip).  This matters
> - * because we want to be confident before sending a "send eoi" auxilary
> + * because we want to be confident before sending a "send eoi" auxiliary
>   * command that we will be able to also put the associated data byte
>   * in the chip before any potential timeout.
>   */
> @@ -316,7 +316,7 @@ static int source_handshake_is_sids_or_sgns(struct fluke_priv *e_priv)
>  
>  /*
>   * Wait until the gpib chip is ready to accept a data out byte.
> - * If the chip is SGNS it is probably waiting for a a byte to
> + * If the chip is SGNS it is probably waiting for a byte to
>   * be written to it.
>   */
>  static int wait_for_data_out_ready(struct gpib_board *board)
> @@ -517,7 +517,7 @@ static int fluke_accel_write(struct gpib_board *board, u8 *buffer, size_t length
>  		/*
>  		 * wait until we are sure we will be able to write the data byte
>  		 * into the chip before we send AUX_SEOI.  This prevents a timeout
> -		 * scenerio where we send AUX_SEOI but then timeout without getting
> +		 * scenario where we send AUX_SEOI but then timeout without getting
>  		 * any bytes into the gpib chip.  This will result in the first byte
>  		 * of the next write having a spurious EOI set on the first byte.
>  		 */
> @@ -547,7 +547,7 @@ static int fluke_get_dma_residue(struct dma_chan *chan, dma_cookie_t cookie)
>  	}
>  	dmaengine_tx_status(chan, cookie, &state);
>  	/*
> -	 * hardware doesn't support resume, so dont call this
> +	 * hardware doesn't support resume, so don't call this
>  	 * method unless the dma transfer is done.
>  	 */
>  	return state.residue;
> -- 
> 2.43.0
> 

Just a friendly reminder

      reply	other threads:[~2026-05-20 22:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 21:19 [PATCH] Drivers: gpib: Fix Typos Michail Tatas
2026-05-20 22:57 ` Michail Tatas [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=ag48b4hk80YzeTwz@michalis-linux \
    --to=michail.tatas@gmail.com \
    --cc=dpenkler@gmail.com \
    --cc=linux-kernel@vger.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