From: Paul Retourne <paul.retourne@orange.fr>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: dpenkler@gmail.com, dan.carpenter@linaro.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/16] staging: gpib: fixes multiline comments style
Date: Tue, 15 Apr 2025 14:38:23 -0700 [thread overview]
Message-ID: <384d030e-e213-4fb3-83fb-cc0d5cb77cf0@orange.fr> (raw)
In-Reply-To: <2025041546-outlet-timid-bca6@gregkh>
On 4/15/25 07:50, Greg KH wrote:
> On Fri, Apr 11, 2025 at 11:21:52PM -0700, Paul Retourné wrote:
>> Fixes the style of multiline comments to comply with the linux kernel
>> coding style as requested in the gpib TODO file.
>>
>> Paul Retourné (16):
>> staging: gpib: agilent_82357a: fixes multiline comments style
>> staging: gpib: cb7210: fixes multiline comments style
>> staging: gpib: common: fixes multiline comments style
>> staging: gpib: eastwood: fixes multiline comments style
>> staging: gpib: fmh_gpib: fixes multiline comments style
>> staging: gpib: gpio: fixes multiline comments style
>> staging: gpib: hp_82335: fixes multiline comments style
>> staging: gpib: hp_82341: fixes multiline comments style
>> staging: gpib: include: fixes multiline comments style
>> staging: gpib: ines: fixes multiline comments style
>> staging: gpib: lpvo_usb_gpib: fixes multiline comments style
>> staging: gpib: nec7210: fixes multiline comments style
>> staging: gpib: ni_usb: fixes multiline comments style
>> staging: gpib: pc2: fixes multiline comments style
>> staging: gpib: tms9914: fixes multiline comments style
>> staging: gpib: tnt4882: fixes multiline comments style
> One of these did not apply to my tree, can you rebase and resend the
> remaining one?
>
> thanks,
>
> greg k-h
Will do, thank you for looking at it,
Paul Retourné
prev parent reply other threads:[~2025-04-15 21:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 6:21 [PATCH 00/16] staging: gpib: fixes multiline comments style Paul Retourné
2025-04-12 6:21 ` [PATCH 01/16] staging: gpib: agilent_82357a: " Paul Retourné
2025-04-12 6:21 ` [PATCH 02/16] staging: gpib: cb7210: " Paul Retourné
2025-04-12 6:21 ` [PATCH 03/16] staging: gpib: common: " Paul Retourné
2025-04-12 6:21 ` [PATCH 04/16] staging: gpib: eastwood: " Paul Retourné
2025-04-12 6:31 ` [PATCH 05/16] staging: gpib: fmh_gpib: " Paul Retourné
2025-04-12 6:34 ` [PATCH 06/16] staging: gpib: gpio: " Paul Retourné
2025-04-12 6:37 ` [PATCH 07/16] staging: gpib: hp_82335: " Paul Retourné
2025-04-12 6:42 ` [PATCH 08/16] staging: gpib: hp_82341: " Paul Retourné
2025-04-12 6:45 ` [PATCH 09/16] staging: gpib: include: " Paul Retourné
2025-04-12 6:47 ` [PATCH 10/16] staging: gpib: ines: " Paul Retourné
2025-04-12 6:48 ` [PATCH 11/16] staging: gpib: lpvo_usb_gpib: " Paul Retourné
2025-04-12 6:49 ` [PATCH 12/16] staging: gpib: nec7210: " Paul Retourné
2025-04-12 7:07 ` [PATCH 13/16] staging: gpib: ni_usb: " Paul Retourné
2025-04-12 7:48 ` [PATCH 14/16] staging: gpib: pc2: " Paul Retourné
2025-04-12 18:09 ` [PATCH 15/16] staging: gpib: tms9914: " Paul Retourné
2025-04-12 18:10 ` [PATCH 16/16] staging: gpib: tnt4882: " Paul Retourné
2025-04-15 14:50 ` [PATCH 00/16] staging: gpib: " Greg KH
2025-04-15 21:38 ` Paul Retourne [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=384d030e-e213-4fb3-83fb-cc0d5cb77cf0@orange.fr \
--to=paul.retourne@orange.fr \
--cc=dan.carpenter@linaro.org \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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