From: "Alexander Grund" <theflamefire89@gmail.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [PATCH 4.4 1/3] ALSA: control: code refactoring for ELEM_READ/ELEM_WRITE operations
Date: Fri, 31 Mar 2023 08:45:21 -0700 [thread overview]
Message-ID: <13330.1680277521000522102@lists.cip-project.org> (raw)
In-Reply-To: <TYWPR01MB9420EB2622E1AE6641A9F0C192899@TYWPR01MB9420.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
Hi,
> Please add original commit id.
becf9e5d553c2389d857a3c178ce80fdb34a02e1
> The original commit doesn't seem to have this tag.
Oof, this gets auto-added when operating/comitting inside the Android tree. Just ignore/remove this.
Do I need to submit the updated patch (actually only the description changes) as a new mail? If so how'd I do that, e.g. with git send-mail?
[-- Attachment #2: Type: text/html, Size: 435 bytes --]
next prev parent reply other threads:[~2023-03-31 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 17:18 [PATCH 4.4 0/3] ALSA: control: Fix locking around snd_ctl_elem_read/write Alexander Grund
2023-03-24 17:18 ` [PATCH 4.4 1/3] ALSA: control: code refactoring for ELEM_READ/ELEM_WRITE operations Alexander Grund
2023-03-29 22:29 ` [cip-dev] " nobuhiro1.iwamatsu
2023-03-31 15:45 ` Alexander Grund [this message]
2023-03-24 17:18 ` [PATCH 4.4 2/3] ALSA: control: Fix memory corruption risk in snd_ctl_elem_read Alexander Grund
2023-03-29 22:33 ` [cip-dev] " nobuhiro1.iwamatsu
2023-03-31 15:52 ` Alexander Grund
2023-03-24 17:18 ` [PATCH 4.4 3/3] ALSA: control: use counting semaphore as write lock for ELEM_WRITE operation Alexander Grund
2023-03-29 22:39 ` [cip-dev] " nobuhiro1.iwamatsu
2023-03-31 15:51 ` Alexander Grund
2023-04-03 8:56 ` [cip-dev] " Ulrich Hecht
2023-04-03 17:13 ` Alexander Grund
2023-04-02 16:30 ` [cip-dev] [PATCH 4.4 0/3] ALSA: control: Fix locking around snd_ctl_elem_read/write Pavel Machek
2023-04-02 18:34 ` Alexander Grund
2023-04-03 8:56 ` [cip-dev] " Ulrich Hecht
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=13330.1680277521000522102@lists.cip-project.org \
--to=theflamefire89@gmail.com \
--cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox