public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ethin Probst" <harlydavidsen@gmail.com>
To: devel@edk2.groups.io
Subject: Re: Status of GSoC 2022 proposal; status of currently implemented functions and protocols related to USB and USB audio
Date: Sat, 30 Apr 2022 01:13:11 -0500	[thread overview]
Message-ID: <a5a8caf4-aef1-1c6b-94b9-76edc14139d6@gmail.com> (raw)
In-Reply-To: <b065e599-2059-d8b7-6ec7-cdc8ca192ab3@gmail.com>

Just inquiring if anyone noticed this. I can see how it'd get lost in 
the noise -- I just haven't heard anything since my initial feedback for 
my proposal. (Or if someone did see this I probably missed it.)

On 4/22/22 13:40, Ethin Probst wrote:
> So this message is a bit of a question and an information dump; if you 
> want me to split this off into two separate discussions that's fine by me.
> First, I'm writing to inquire about the status of my proposal; I 
> received some feedback and believe I corrected my proposal as directed, 
> but unless it got lost in the flood of emails I get I have yet to hear 
> anything about that, so I thought I'd inquire as to if anything has 
> happened on that front.
> Second, I've been digging through the EDK II sources (as of commit 
> ee582858c4) and I've decided that it would be helpful to list all the 
> functions/protocols that need implementation for my project. I'm however 
> unsure how to scan for what and what is not implemented without writing 
> an application and testing for each protocol. Is there a more efficient 
> way for me to look for these?

      reply	other threads:[~2022-04-30  6:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cbda9f00-d294-9fcc-d876-fe2bb6e33ba4@gmail.com>
2022-04-22 18:40 ` Status of GSoC 2022 proposal; status of currently implemented functions and protocols related to USB and USB audio Ethin Probst
2022-04-30  6:13   ` Ethin Probst [this message]

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-list 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=a5a8caf4-aef1-1c6b-94b9-76edc14139d6@gmail.com \
    --to=devel@edk2.groups.io \
    /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