From: "Alexander Grund" <theflamefire89@gmail.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [PATCH 4.4 0/3] ALSA: control: Fix locking around snd_ctl_elem_read/write
Date: Sun, 02 Apr 2023 11:34:02 -0700 [thread overview]
Message-ID: <24425.1680460442746826724@lists.cip-project.org> (raw)
In-Reply-To: <ZCmtowC1mia0A1Cx@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
>
> Second option is to cherry-pick these:
That's exactly what I did here. From my submissions to the upstream kernels I was told that a 0/x EMail is required for a multi-commit change.
I haven't found a guideline how to submit patches to CIP kernels, so I just followed that procedure. See: https://lists.cip-project.org/g/cip-dev/message/11117 https://lists.cip-project.org/g/cip-dev/message/11118 https://lists.cip-project.org/g/cip-dev/message/11119
It seems that was wrong. So can you tell me please how to submit patches to CIP in the future and whether the current mails are acceptable (despite the minor description changes requested there)?
Thanks,
Alex
[-- Attachment #2: Type: text/html, Size: 1028 bytes --]
next prev parent reply other threads:[~2023-04-02 18:34 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
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 [this message]
2023-04-03 8:56 ` 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=24425.1680460442746826724@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