From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: " \(alsa-devel@alsa-project.org\)" <alsa-devel@alsa-project.org>
Subject: Re: Turn on power early to avoid something
Date: Fri, 30 Dec 2022 10:15:44 +0100 [thread overview]
Message-ID: <87cz81xnen.wl-tiwai@suse.de> (raw)
In-Reply-To: <af64a2d5e55448dbadef4d0efd96bea5@realtek.com>
On Fri, 30 Dec 2022 09:14:16 +0100,
Kailang wrote:
>
>
>
> > -----Original Message-----
> > From: Takashi Iwai <tiwai@suse.de>
> > Sent: Friday, December 30, 2022 4:05 PM
> > To: Kailang <kailang@realtek.com>
> > Cc: (alsa-devel@alsa-project.org) <alsa-devel@alsa-project.org>
> > Subject: Re: Turn on power early to avoid something
> >
> > On Fri, 30 Dec 2022 08:54:01 +0100,
> > Kailang wrote:
> > >
> > > Hi Takashi,
> > >
> > > It maybe can avoid something for early power up.
> > >
> > > Many Thanks.
> > > Kailang.
> >
> > Hmm, what is "something"? The description is way too ambiguous to judge
> > whether the change is OK or not, unfortunately.
> > Could you elaborate what exactly the change will fix?
> >
> > Also, when you submit a patch from another person, please put your own
> > Signed-off-by line. It's a legal requirement.
> yangyuchi66@gmail.com was my personal account.
> Could I use this account?
Ah OK, then it's fine.
> Or I need use this account to mail patch to you.
It's not necessary, the sign-off is fine as long as it matches with
the From address in the patch and it's yourself.
But we still need a better description of the patch text.
thanks,
Takashi
next prev parent reply other threads:[~2022-12-30 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 7:54 Turn on power early to avoid something Kailang
2022-12-30 8:04 ` Takashi Iwai
2022-12-30 8:14 ` Kailang
2022-12-30 9:15 ` Takashi Iwai [this message]
2023-01-03 6:51 ` Kailang
2023-01-03 15:13 ` Takashi Iwai
2022-12-30 8:48 ` Kailang
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=87cz81xnen.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kailang@realtek.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.