From: Jeremy Dean Clifton <gservice341@gmail.com>
To: Comfort Oyewole <coyewole7@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: comedi: comedi_fops: fix alignment to match open parenthesis
Date: Mon, 19 Oct 2026 20:20:33 -0600 [thread overview]
Message-ID: <cdcaf727-4433-4f8c-8e33-42094efcc6d8@gmail.com> (raw)
In-Reply-To: <53D6A234-940A-4B29-89B2-7EB0E459F077@inria.fr>
On 10/18/26 11:09 AM, Julia Lawall wrote:
>
>
>> On 18 Oct 2026, at 10:18, Comfort Oyewole <coyewole7@gmail.com> wrote:
>>
>> -----Original Message-----
>> From: Greg KH <gregkh@linuxfoundation.org>
>> To: Comfort Oyewole <coyewole7@gmail.com>
>> Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
>> linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
>> outreachy@lists.linux.dev
>> Subject: Re: [PATCH] staging: comedi: comedi_fops: fix alignment to
>> match open parenthesis
>> Date: 10/18/2026 02:30:05 PM
>>
>>> On Sun, Oct 18, 2026 at 02:22:49PM +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(-)
>>
>> This is not a staging driver, why is staging in the subject line and the
>> cc list?
>> Sorry, I made a mistake while working on my first patch. I just realised the staging drivers are located under drivers/staging dir.
>> Is there anything I can do to correct this?
>
> Just work on something else.
>
Comfort,
The comedi driver isn't part of staging. You can see who looks after it
in the MAINTAINERS file
or with:
./scripts/get_maintainer.pl -f drivers/comedi/comedi_fops.c
That lists Ian Abbott and H Hartley Sweeten as maintainers, with
linux-kernel@vger.kernel.org as the list.
There's no dedicated patchwork for comedi. Some subsystems do have one.
https://patchwork.kernel.org/
Drivers outside staging have different
expectations. A clean-up style fix may not warrant a change.
You can still send it if you'd like to see that change in the driver,
but I think it could be separate from Outreachy and staging.
Good luck with your next patch.
Jeremy
> Julia
>
>>
>
next prev parent reply other threads:[~2026-10-20 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2026-10-20 2:20 ` Jeremy Dean Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-18 13:10 Comfort Oyewole
2026-10-18 13:30 ` Greg KH
2026-10-18 14:26 ` Comfort Oyewole
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=cdcaf727-4433-4f8c-8e33-42094efcc6d8@gmail.com \
--to=gservice341@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=coyewole7@gmail.com \
--cc=hsweeten@visionengravers.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®