From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Kalle Valo <kvalo@codeaurora.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
"David S. Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] mac80211: fix memory leak
Date: Mon, 1 Feb 2016 15:57:09 +0300 [thread overview]
Message-ID: <56AF5625.5030701@cogentembedded.com> (raw)
In-Reply-To: <878u34u6d6.fsf@purkki.adurom.net>
Hello.
On 2/1/2016 12:28 PM, Kalle Valo wrote:
>> 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
>>> <sudipm.mukherjee@gmail.com> wrote:
>>>> On error we jumped to the error label and returned the error code but we
>>>> missed releasing sinfo.
>>>>
>>>> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
>>>
>>> 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.
Documentation/SubmittingPatches, clause 14.
MBR, Sergei
next prev parent reply other threads:[~2016-02-01 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 9:49 [PATCH] mac80211: fix memory leak Sudip Mukherjee
2016-02-01 0:03 ` Julian Calaby
2016-02-01 4:25 ` Sudip Mukherjee
2016-02-01 4:30 ` Julian Calaby
2016-02-01 4:30 ` Julian Calaby
2016-02-01 9:28 ` Kalle Valo
2016-02-01 9:33 ` Sudip Mukherjee
2016-02-01 10:23 ` Julian Calaby
2016-02-01 12:57 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-20 9:37 Johannes Berg
2014-02-06 19:01 Emmanuel Grumbach
2014-02-11 11:59 ` Johannes Berg
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=56AF5625.5030701@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=julian.calaby@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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.