From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
devel@driverdev.osuosl.org,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@broadcom.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eric Anholt <eric@anholt.net>,
Michael Zoran <mzoran@crowfest.net>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
linux-rpi-kernel@lists.infradead.org, Ray Jui <rjui@broadcom.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4] staging: bcm2835-audio: Release resources on module_exit()
Date: Sun, 25 Mar 2018 12:44:44 +0200 [thread overview]
Message-ID: <4e473a93-317a-5777-7444-6deb105c8f66@gmail.com> (raw)
In-Reply-To: <CAHp75VfJjCHd5U1D22NANLCA1kAoTKLnDGSQPj3ay6OhKSoZxg@mail.gmail.com>
On 03/25/18 12:33, Andy Shevchenko wrote:
> On Fri, Mar 23, 2018 at 9:22 PM, Kirill Marinushkin
> <k.marinushkin@gmail.com> wrote:
>> On 03/23/18 17:23, Andy Shevchenko wrote:
>>> After addressing above, FWIW,
>>>
>>> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Seems you missed my tag in new version.
> When someone gives you a tag and you are going to send a new version
> (w/o drastic changes), it's your responsibility to append it
>
> I will send a new mail with it, so, this time no need to resend. Just
> keep it for the future contributions.
>
What is a "tag"?
I added in-reply-to this email, I added you as CC.
Isn't it enough to keep track of the versioning within a mailing list?
Could you please clarify: what "tag" should I usually attach in addition?
Best Regards,
Kirill
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-03-25 10:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 5:52 [PATCH] staging: bcm2835-audio: Release resources on module_exit() Kirill Marinushkin
2018-03-06 12:14 ` Greg Kroah-Hartman
2018-03-06 17:42 ` Kirill Marinushkin
2018-03-13 19:34 ` [PATCH v2] " Kirill Marinushkin
2018-03-13 21:23 ` Andy Shevchenko
2018-03-15 5:57 ` Kirill Marinushkin
2018-03-21 15:03 ` Andy Shevchenko
2018-03-21 16:58 ` Kirill Marinushkin
2018-03-21 18:48 ` [PATCH v3] " Kirill Marinushkin
2018-03-21 19:24 ` Andy Shevchenko
2018-03-21 19:51 ` Kirill Marinushkin
2018-03-22 21:21 ` Kirill Marinushkin
2018-03-22 21:37 ` [PATCH v4] " Kirill Marinushkin
2018-03-23 16:23 ` Andy Shevchenko
2018-03-23 19:22 ` Kirill Marinushkin
2018-03-25 10:33 ` Andy Shevchenko
2018-03-25 10:44 ` Kirill Marinushkin [this message]
2018-03-25 13:03 ` Andy Shevchenko
2018-03-25 13:54 ` Kirill Marinushkin
2018-03-23 19:32 ` [PATCH v5] " Kirill Marinushkin
2018-03-25 10:33 ` Andy Shevchenko
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=4e473a93-317a-5777-7444-6deb105c8f66@gmail.com \
--to=k.marinushkin@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mzoran@crowfest.net \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).