Messages in this thread | | | From | Andy Shevchenko <> | Date | Sun, 25 Mar 2018 16:03:41 +0300 | Subject | Re: [PATCH v4] staging: bcm2835-audio: Release resources on module_exit() |
| |
On Sun, Mar 25, 2018 at 1:44 PM, Kirill Marinushkin <k.marinushkin@gmail.com> wrote: > 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?
Section 13) in Submitting Patches [1] explains that.
[1]: https://elixir.bootlin.com/linux/v4.16-rc6/source/Documentation/process/submitting-patches.rst
-- With Best Regards, Andy Shevchenko
| |