From: Krzysztof Kozlowski <krzk@kernel.org>
To: ShiHao <i.shihao.999@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, broonie@kernel.org,
bjorn.andersson@oss.qualcomm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: request for guidence
Date: Wed, 18 Mar 2026 15:15:56 +0100 [thread overview]
Message-ID: <40d02335-90c2-4b14-a9df-d9ff1a75ddd2@kernel.org> (raw)
In-Reply-To: <abqr0Qpcx_2BQINg@fedora>
On 18/03/2026 14:42, ShiHao wrote:
> On Wed, Mar 18, 2026 at 01:53:25PM +0100, Krzysztof Kozlowski wrote:
>
>> Hey,
>>
>> None of the people you Cc-ed here is involved in GSoC. You reached Linux
>> kernel community, which has nothing to do with GSoC. I suggest
>> contacting GSoC through whatever contact form the provided you on the
>> application.
>>
>> Best regards,
>> Krzysztof
>
>
> hello Krzysztof,
>
> Thanks for your response. However i mailed them and got no
> response. It was instructed on the page to contact respective
> mainling list. Also my mentors seems to be busy I submitted several
I could not find any GSoC page telling that DT is the respective list to
contact about your application. Or that me or Mark or Bjorn are... Where
did you find it, so we can ask GSoC organizers to correct the docs?
> DT conversion got no rely till now. The application period has began
> i don't know whom should i discuss all this then my mentros.
On the GSoC pages, there is list of people from Linux Foundation to
reach. Unfortunately I do not know with whom else you could contact, but
I am sure that Linux kernel maintainers are not the ones to discuss it.
GSoC is Google's or Linux Foundation program, nothing to do with us.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-18 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 12:32 request for guidence ShiHao
2026-03-18 12:53 ` Krzysztof Kozlowski
2026-03-18 13:42 ` ShiHao
2026-03-18 14:15 ` Krzysztof Kozlowski [this message]
2026-03-19 9:17 ` ShiHao
2026-03-19 9:27 ` Krzysztof Kozlowski
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=40d02335-90c2-4b14-a9df-d9ff1a75ddd2@kernel.org \
--to=krzk@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=i.shihao.999@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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