From: Julia Lawall <julia.lawall@lip6.fr>
To: Evan Chime <chime.evan.dri.devel@gmail.com>
Cc: gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com,
laurent.pinchart@ideasonboard.com, mchehab@kernel.org
Subject: Re: [Outreachy kernel] [PATCH v2 0/3] Add comment to memory barrier
Date: Sun, 3 Nov 2019 17:18:03 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1911031716390.2557@hadrien> (raw)
In-Reply-To: <cover.1572797322.git.chime.evan.dri.devel@gmail.com>
On Sun, 3 Nov 2019, Evan Chime wrote:
> Include outreachy mailing list in "cc" list. No change
>
> Evan Chime (3):
> Staging: media: omap4iss: Add comment to memory barrier
> Staging: media: omap4iss: Add comment to memory barrier
> Staging: media: omap4iss: Add comment to memory barrier
Each patch should have a different subject. If you end up with patches
with the same subject, you should make the subjects more specific or merge
them.
In this case, though, I think that this is an issue that only someone with
a deep knowledge of the code could really address. The question is not
what a memory barrier does, but why one is needed at a particular place in
the code.
julia
>
> drivers/staging/media/omap4iss/iss.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --
> 2.17.1
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/cover.1572797322.git.chime.evan.dri.devel%40gmail.com.
>
next prev parent reply other threads:[~2019-11-03 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 16:13 [PATCH v2 0/3] Add comment to memory barrier Evan Chime
2019-11-03 16:14 ` [PATCH v2 1/3] Staging: media: omap4iss: " Evan Chime
2019-11-03 17:07 ` Greg KH
2019-11-03 17:26 ` evan chime
2019-11-03 16:14 ` [PATCH v2 2/3] " Evan Chime
2019-11-03 16:15 ` [PATCH v2 3/3] " Evan Chime
2019-11-03 16:16 ` [Outreachy kernel] " Julia Lawall
2019-11-03 16:23 ` evan chime
2019-11-03 16:18 ` Julia Lawall [this message]
2019-11-03 16:27 ` [Outreachy kernel] [PATCH v2 0/3] " evan chime
2019-11-04 13:26 ` evan chime
2019-11-04 18:54 ` evan chime
2019-11-05 16:40 ` ledepiele
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=alpine.DEB.2.21.1911031716390.2557@hadrien \
--to=julia.lawall@lip6.fr \
--cc=chime.evan.dri.devel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=mchehab@kernel.org \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.