From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Penkler <dpenkler@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Marcello Carla' <marcello.carla@gmx.com>
Subject: Re: [PATCH 3/4] staging: gpib: Fix erroneous removal of blank before newline
Date: Wed, 4 Dec 2024 16:29:43 +0100 [thread overview]
Message-ID: <2024120410-claim-precut-61e3@gregkh> (raw)
In-Reply-To: <20241204145713.11889-4-dpenkler@gmail.com>
On Wed, Dec 04, 2024 at 03:57:12PM +0100, Dave Penkler wrote:
> Replace original blanks with "."
>
> Reported-by: Marcello Carla' <marcello.carla@gmx.com>
> Co-developed-by: Marcello Carla' <marcello.carla@gmx.com>
> Fixes: fce79512a96a ("staging: gpib: Add LPVO DIY USB GPIB driver")
> Signed-off-by: Dave Penkler <dpenkler@gmail.com>
> ---
> drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c b/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
> index 47db17418a74..c30db3615f49 100644
> --- a/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
> +++ b/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
> @@ -97,8 +97,8 @@ module_param(debug, int, 0644);
> #define USB_GPIB_DEBUG_ON "\nIBDE\xAA\n"
> #define USB_GPIB_SET_LISTEN "\nIBDT0\n"
> #define USB_GPIB_SET_TALK "\nIBDT1\n"
> -#define USB_GPIB_SET_LINES "\nIBDC\n"
> -#define USB_GPIB_SET_DATA "\nIBDM\n"
> +#define USB_GPIB_SET_LINES "\nIBDC.\n"
> +#define USB_GPIB_SET_DATA "\nIBDM.\n"
> #define USB_GPIB_READ_LINES "\nIBD?C\n"
> #define USB_GPIB_READ_DATA "\nIBD?M\n"
> #define USB_GPIB_READ_BUS "\nIBD??\n"
> @@ -587,7 +587,7 @@ static int usb_gpib_command(gpib_board_t *board,
> size_t *bytes_written)
> {
> int i, retval;
> - char command[6] = "IBc\n";
> + char command[6]="IBc.\n";
Did you run this through scripts/checkpatch.pl before sending it out?
Please always do so.
And what is the "." for? Why is this needed? Please explain that in
the changelog text.
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-04 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 14:57 [PATCH 0/4] staging: gpib: Cleanup and fixes for lpvo driver Dave Penkler
2024-12-04 14:57 ` [PATCH 1/4] staging: gpib: Remove useless include Dave Penkler
2024-12-04 14:57 ` [PATCH 2/4] staging: gpib: Remove duplicate include Dave Penkler
2024-12-04 14:57 ` [PATCH 3/4] staging: gpib: Fix erroneous removal of blank before newline Dave Penkler
2024-12-04 15:29 ` Greg KH [this message]
2024-12-04 16:05 ` Dan Carpenter
2024-12-04 14:57 ` [PATCH 4/4] staging: gpib: Fix faulty workaround for assignment in if Dave Penkler
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=2024120410-claim-precut-61e3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=marcello.carla@gmx.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