netdev - Re: [PATCH 1/1] net/fec: do not pass NULL dev to DMA API

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 02 Apr 2011 01:35:41 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	liu.h.jason@...il.com
Cc:	shawn.guo@...escale.com, netdev@...r.kernel.org,
	b29396@...escale.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/1] net/fec: do not pass NULL dev to DMA API

From: Jason Liu <liu.h.jason@...il.com>
Date: Sat, 2 Apr 2011 16:35:19 +0800

> 2011/4/2 Shawn Guo <shawn.guo@...escale.com>:
>> Hi David,
>>
>> On Sat, Apr 02, 2011 at 12:57:14AM -0700, David Miller wrote:
>>>
>>> First, your patches never make it to the mailing list because the list
>>> server rejects your postings, due to the fact that there are syntax
>>> errors in your email headers:
>>>
>>> Illegal-Object:       Syntax error in From: address found on vger.kernel.org:
>>>       From:   Aisheng.Dong<b29396@...escale.com>
>>>                                   ^-missing end of mailbox
>>>
>> Yes, we were aware of that the mail did not get distributed by vger
>> list.  But we do not know why.  Thanks for telling.
>>
>> I'm not quite sure about the "^" indication.  Is it telling that there
>> should be a space between display name and mail address?
> 
> We should not use A.B <>, instead should use A B <>.

Yes, this is also true.

Characters such as "." must not appear in email headers in this
context unless protected by double quotes.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html