All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: marcel <marcelg@gmx.com>
Cc: ALSA-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] Add Asus VivoBook S 16X to quirks table for acp6x
Date: Wed, 20 Mar 2024 00:40:03 -0300	[thread overview]
Message-ID: <Zfpak4MeAusZUePK@geday> (raw)
In-Reply-To: <7bbc4afe-30de-4342-953d-2cddcb3c7933@gmx.com>

On Tue, Mar 19, 2024 at 05:16:10PM +0800, marcel wrote:
> Hi again,
> 
> it's been a while since i sent my patch and I still can't see it in
> kernel on github, so there's my question because I'm not sure if I
> understand correctly. Should I just wait a little bit more and it just
> takes time or send patch again and change things you pointed? Also which
> version should I type after [PATCH v...], "1" ? Because it's my first
> attempt? Sorry for taking your time and if the questions are obvious,
> but it's my first time doing something like this.

Hi Marcel, please address my past concerns regarding your patch and
resubmit as v2.

Remember to Cc: Takashi Iwai and Jaroslav Kysela besides linux-sound
mailing list or your patch will fall into limbo again, overlooked by the
maintainers.

There's also a get_maintainers.pl script in the linux tree. You might
wanna use that as it adds some relevant people who might take a interest
in your patch.

Thanks,
Geraldo Nascimento

> 
> Greetings

      parent reply	other threads:[~2024-03-20  3:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05  3:48 [PATCH] Add Asus VivoBook S 16X to quirks table for acp6x marcel
2024-02-06  2:37 ` Geraldo Nascimento
     [not found]   ` <1b37b9ee-68db-425c-b878-71847459fb3c@gmx.com>
     [not found]     ` <7bbc4afe-30de-4342-953d-2cddcb3c7933@gmx.com>
2024-03-20  3:40       ` Geraldo Nascimento [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-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=Zfpak4MeAusZUePK@geday \
    --to=geraldogabriel@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=marcelg@gmx.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.