All of lore.kernel.org
 help / color / mirror / Atom feed
From: ShiHao <i.shihao.999@gmail.com>
To: Krzysztof Kozlowski <krzk@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 19:12:41 +0530	[thread overview]
Message-ID: <abqr0Qpcx_2BQINg@fedora> (raw)
In-Reply-To: <ccce197c-c514-43c8-8026-534966bb0438@kernel.org>

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
      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.

Best regards
 shihao

  reply	other threads:[~2026-03-18 13:43 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
2026-03-18 13:42   ` ShiHao [this message]
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=abqr0Qpcx_2BQINg@fedora \
    --to=i.shihao.999@gmail.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@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.