From: Comfort Oyewole <coyewole7@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: abbotti@mev.co.uk, hsweeten@visiongravers.com,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: comedi: comedi_fops: fix alignment to match open parenthesis
Date: Sun, 18 Oct 2026 15:26:20 +0100 [thread overview]
Message-ID: <b7a4167f8e188d7a0dfe72c2a3e6e51337a33336.camel@gmail.com> (raw)
In-Reply-To: <2026101818-banish-scarf-eb6e@gregkh>
-----Original Message-----
From: Greg KH <gregkh@linuxfoundation.org>
To: Comfort Oyewole <coyewole7@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visiongravers.com,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: comedi: comedi_fops: fix alignment to
match open parenthesis
Date: 10/18/2026 02:30:28 PM
On Sun, Oct 18, 2026 at 02:10:39PM +0100, Comfort Oyewole wrote:
> Fix the alignment issue in order to adhere to kernel coding style
>
> Signed-off-by: Comfort Oyewole <coyewole7@gmail.com>
> ---
> drivers/comedi/comedi_fops.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Why was this sent twice?
I apologize for the duplicate email. I thought my mutt configuration didn't work the first time.
next prev parent reply other threads:[~2026-10-18 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 13:10 Comfort Oyewole
2026-10-18 13:30 ` Greg KH
2026-10-18 14:26 ` Comfort Oyewole [this message]
2026-10-18 13:22 Comfort Oyewole
2026-10-18 13:30 ` Greg KH
2026-10-18 14:16 ` Comfort Oyewole
2026-10-18 17:09 ` Julia Lawall
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=b7a4167f8e188d7a0dfe72c2a3e6e51337a33336.camel@gmail.com \
--to=coyewole7@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visiongravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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
all inboxes | Powered by JetHome®