From: "Alexander Grund" <theflamefire89@gmail.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [PATCH 4.4 3/3] ALSA: control: use counting semaphore as write lock for ELEM_WRITE operation
Date: Mon, 03 Apr 2023 10:13:06 -0700 [thread overview]
Message-ID: <6415.1680541986353766715@lists.cip-project.org> (raw)
In-Reply-To: <913352448.1492969.1680512218678@webmail.strato.com>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
>
> Please add backports commit id.
I would have added this below the first line (after an empty line):
>
> commit 5bbb1ab5bd0b01c4f0b19ae03fdfec487f839517 upstream.
Would that have been correct? Or would something else have been required in addition?
>
>
>
> Normally, even for small changes, you would re-format the whole series
> with "git format-patch --cover-letter --subject-prefix 'PATCH v2'" and
> send it all again with git send-mail, adding a note to the cover letter on
> what has changed in this revision.
>
>
So it isn't a problem that this opens a new (series of) threads instead of replying to the mails requesting the changes, is it?
I use `git send-email` directly (I have set sendemail.annotate=true & sendemail.confirm=always), so my command would have looked like this: `git send-email --cover-letter --subject-prefix="PATCH v2" --suppress-cc=all --to=cip-dev@lists.cip-project.org cip/linux-4.4.y-st..fix-alsa` which is basically how I created the current 4 mails.
I'm wondering if this is correct, especially as I used the prefix "PATCH 4.4" before to denote that it is meant for the 4.4.y branch. This doesn't seem to be required, so what should I use as the prefix instead for a (future) patch/patch series?
Anyway I noticed you already applied the commits fixing the mentioned issues before tagging, thanks!
I'd still appreciate a reply or a link to a page answering those question if one already exists, so the process can be smoother next time.
Thanks a lot!
[-- Attachment #2: Type: text/html, Size: 1632 bytes --]
next prev parent reply other threads:[~2023-04-03 17:13 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 [this message]
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=6415.1680541986353766715@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