From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752822AbcBAJ2q (ORCPT ); Mon, 1 Feb 2016 04:28:46 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:37112 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751513AbcBAJ2o (ORCPT ); Mon, 1 Feb 2016 04:28:44 -0500 From: Kalle Valo To: Sudip Mukherjee Cc: Julian Calaby , Johannes Berg , "David S. Miller" , "linux-kernel\@vger.kernel.org" , linux-wireless , netdev Subject: Re: [PATCH] mac80211: fix memory leak References: <1454060944-11320-1-git-send-email-sudipm.mukherjee@gmail.com> <20160201042548.GA4072@sudip-pc> Date: Mon, 01 Feb 2016 11:28:37 +0200 In-Reply-To: <20160201042548.GA4072@sudip-pc> (Sudip Mukherjee's message of "Mon, 1 Feb 2016 09:55:48 +0530") Message-ID: <878u34u6d6.fsf@purkki.adurom.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sudip Mukherjee writes: > On Mon, Feb 01, 2016 at 11:03:35AM +1100, Julian Calaby wrote: >> Hi Sudip, >> >> On Fri, Jan 29, 2016 at 8:49 PM, Sudip Mukherjee >> wrote: >> > On error we jumped to the error label and returned the error code but we >> > missed releasing sinfo. >> > >> > Signed-off-by: Sudip Mukherjee >> >> Should the From: and Signed-off-by: email addresses be the same? > > I think 2 years back I had a long discussion with Greg about this and > since then I al submitting patches like this. A small summayg of the > problem from that discussion: > > "we have strict DMARC check for the corporate mail server. DMARC = > domain based message authentication. > So the mail i sent reached all the list subscriber from a different > server than our designated server, and as a result it is marked as spam > in many places and I have already received a few complaints regarding > that." You can add a separate "From:" line to the beginning of the commit log and git will use it then commiting the patch. I didn't find any documention but it's easy to do and should solve this. -- Kalle Valo