From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH 01/16] xen/events: refactor retrigger_dynirq() and resend_irq_on_evtchn() Date: Wed, 2 Oct 2013 17:08:15 -0400 Message-ID: <20131002210815.GA25661@phenom.dumpdata.com> References: <1380734101-2991-1-git-send-email-david.vrabel@citrix.com> <1380734101-2991-2-git-send-email-david.vrabel@citrix.com> <20131002204335.GA25399@phenom.dumpdata.com> <524C8999.5020508@cantab.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <524C8999.5020508@cantab.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel Cc: Boris Ostrovsky , David Vrabel , Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Wed, Oct 02, 2013 at 10:01:13PM +0100, David Vrabel wrote: > On 02/10/2013 21:43, Konrad Rzeszutek Wilk wrote: > > On Wed, Oct 02, 2013 at 06:14:46PM +0100, David Vrabel wrote: > >> From: David Vrabel > >> > >> These two function did the same thing with different parameters, put > >> the common bits in retrigger_evtchn(). > >> > >> This changes the return value of resend_irq_on_evtchn() but the only > >> caller (in arch/ia64/xen/irq_xen.c) ignored the return value so this > >> is fine. > >> > >> Signed-off-by: David Vrabel > > > > Hm, I thought I acked it? > > You said "Looks good to me" which wasn't official enough to add as a tag. It is in the Linux kernel, see Documentation/SubmittingPatches: 13) When to use Acked-by: and Cc: The Signed-off-by: tag indicates that the signer was involved in the development of the patch, or that he/she was in the patch's delivery path. If a person was not directly involved in the preparation or handling of a patch but wishes to signify and record their approval of it then they can arrange to have an Acked-by: line added to the patch's changelog. Acked-by: is often used by the maintainer of the affected code when that maintainer neither contributed to nor forwarded the patch. Acked-by: is not as formal as Signed-off-by:. It is a record that the acker has at least reviewed the patch and has indicated acceptance. Hence patch mergers will sometimes manually convert an acker's "yep, looks good to me" into an Acked-by:. > > David