From: Krzysztof Kozlowski <krzk@kernel.org>
To: ShiHao <i.shihao.999@gmail.com>, krzk+dt@kernel.org
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 13:53:25 +0100 [thread overview]
Message-ID: <ccce197c-c514-43c8-8026-534966bb0438@kernel.org> (raw)
In-Reply-To: <abqbUuruxPJsfBo3@fedora>
On 18/03/2026 13:32, ShiHao wrote:
> Hello everyone,
>
> I hope everyone is good. I am writing this letter to ask forsome guidance
> on GSoC. I wanted some help regarding proposal since the application
> period has began i wanted to ask whether to submit my prepared proposal
> or not and wait for review by mentors first because the proposal template
> is a bit different from google's suggested template that is why i have
> some confusions. If anyone has some time to review my drafted proposal i
> would be very thankful. Any help would be deeply appreciated
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
next prev parent reply other threads:[~2026-03-18 12:53 UTC|newest]
Thread overview: 13+ 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 [this message]
2026-03-18 13:42 ` ShiHao
2026-03-18 14:15 ` Krzysztof Kozlowski
2026-03-19 9:17 ` ShiHao
2026-03-19 9:27 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2026-03-06 5:18 Request " ShiHao
2026-03-07 21:43 ` Marcelo Schmitt
2026-03-09 4:14 ` ShiHao
2026-03-09 22:55 ` Till Kamppeter
2026-03-10 10:28 ` Andy Shevchenko
2026-03-11 5:13 ` ShiHao
2026-03-22 12:06 ` Jonathan Cameron
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=ccce197c-c514-43c8-8026-534966bb0438@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=krzk+dt@kernel.org \
--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 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.