From: Markus Elfring <Markus.Elfring@web.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-aspeed@lists.ozlabs.org, linux-usb@vger.kernel.org,
kernel-janitors@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Ma Ke <make24@iscas.ac.cn>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Joel Stanley <joel@jms.id.au>,
Julia Lawall <julia.lawall@inria.fr>,
Neal Liu <neal_liu@aspeedtech.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v4] usb: gadget: aspeed_udc: validate endpoint index for ast udc
Date: Tue, 25 Jun 2024 18:12:18 +0200 [thread overview]
Message-ID: <fcb2c59a-b0e2-4a07-853d-8dda94db628e@web.de> (raw)
In-Reply-To: <2024062553-koala-granddad-50f1@gregkh>
>> You indicated concerns according to patch review processes,
>> didn't you?
>>
>> See also:
>> * Patch submission notes
>> https://elixir.bootlin.com/linux/v6.10-rc5/source/Documentation/process/maintainer-tip.rst#L100
>
> This is not the tip tree.
I know.
But I got the impression that some information sources
(also from the Linux development reference documentation)
can provide advices and further guidance for recurring patch review concerns.
>> I might be going to influence evolution of this software area in other ways
>> under other circumstances.
>
> Please take some time and find other projects to help out.
I found several opportunities already to improve something through the years.
Concrete example for a selected data representation:
https://patchwork.kernel.org/project/linux-usb/list/?submitter=170303&archive=both
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: linux-aspeed@lists.ozlabs.org
Subject: [v4] usb: gadget: aspeed_udc: validate endpoint index for ast udc
Date: Tue, 25 Jun 2024 18:12:18 +0200 [thread overview]
Message-ID: <fcb2c59a-b0e2-4a07-853d-8dda94db628e@web.de> (raw)
In-Reply-To: <2024062553-koala-granddad-50f1@gregkh>
>> You indicated concerns according to patch review processes,
>> didn't you?
>>
>> See also:
>> * Patch submission notes
>> https://elixir.bootlin.com/linux/v6.10-rc5/source/Documentation/process/maintainer-tip.rst#L100
>
> This is not the tip tree.
I know.
But I got the impression that some information sources
(also from the Linux development reference documentation)
can provide advices and further guidance for recurring patch review concerns.
>> I might be going to influence evolution of this software area in other ways
>> under other circumstances.
>
> Please take some time and find other projects to help out.
I found several opportunities already to improve something through the years.
Concrete example for a selected data representation:
https://patchwork.kernel.org/project/linux-usb/list/?submitter=170303&archive=both
Regards,
Markus
next prev parent reply other threads:[~2024-06-25 16:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 2:23 [PATCH v4] usb: gadget: aspeed_udc: validate endpoint index for ast udc Ma Ke
2024-06-25 2:23 ` Ma Ke
2024-06-25 12:00 ` Markus Elfring
2024-06-25 12:00 ` Markus Elfring
2024-06-25 12:29 ` Greg Kroah-Hartman
2024-06-25 12:29 ` Greg Kroah-Hartman
2024-06-25 12:30 ` Greg Kroah-Hartman
2024-06-25 12:30 ` Greg Kroah-Hartman
2024-06-25 12:50 ` Markus Elfring
2024-06-25 12:50 ` Markus Elfring
2024-06-25 14:30 ` Greg Kroah-Hartman
2024-06-25 14:30 ` Greg Kroah-Hartman
2024-06-25 15:20 ` Markus Elfring
2024-06-25 15:20 ` Markus Elfring
2024-06-25 15:25 ` Greg Kroah-Hartman
2024-06-25 15:25 ` Greg Kroah-Hartman
2024-06-25 16:12 ` Markus Elfring [this message]
2024-06-25 16:12 ` [v4] " Markus Elfring
2024-06-26 8:55 ` [RFC] usb: Patch review processes? Markus Elfring
2024-06-26 8:55 ` Markus Elfring
2024-06-26 0:07 ` [PATCH v4] usb: gadget: aspeed_udc: validate endpoint index for ast udc Andrew Jeffery
2024-06-26 0:07 ` Andrew Jeffery
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=fcb2c59a-b0e2-4a07-853d-8dda94db628e@web.de \
--to=markus.elfring@web.de \
--cc=andrew@codeconstruct.com.au \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=neal_liu@aspeedtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.