linux-kernel - RE: [PATCH] staging/dt3155: fix build error caused by {write|read}l change

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]

Message-ID: <0D753D10438DA54287A00B0270842697636D367AAB@AUSP01VMBX24.collaborationhost.net>
Date:	Thu, 8 Apr 2010 16:07:12 -0500
From:	H Hartley Sweeten <hartleys@...ionengravers.com>
To:	Greg KH <greg@...ah.com>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>,
	"ss@....gov.au" <ss@....gov.au>
Subject: RE: [PATCH] staging/dt3155: fix build error caused by {write|read}l
 change

On Thursday, April 08, 2010 1:46 PM, Greg KH wrote:
> On Thu, Apr 08, 2010 at 03:38:06PM -0500, H Hartley Sweeten wrote:
>> On Thursday, April 08, 2010 12:11 PM, Greg KH wrote:
>>> On Wed, Mar 03, 2010 at 11:24:06AM -0700, H Hartley Sweeten wrote:
>>>> This fixes a build error caused by replacing {Write | Read}MReg with 
>>>> {write | read}l.
>>>
>>> Ick, can you merge this with your other patch so we don't have build
>>> errors?  I just hit this and I had to drop all of your patches.
>> 
>> I was expecting you to NAK all of them anyway after I saw all the code 
>> cleanup patches coming in on LKML.
>> 
>>> Can you respin all of them please?
>> 
>> Not a problem.  Are you planning on merging any of the dt3155 cleanup
>> patches?  If so I will wait until they show up.
>
> I took some, you should have gotten the responses now.

I wasn't on the CC list for the ones I noticed on LKML.

A lot of the patches I saw seemed to be duplicate works to clean up the
files.  Plus, some of them appeared that they would conflict in various
ways.  I guess such is the life of a staging driver...

>> Also, should staging patches be based on linux-next or on Linus' git tree?
>
> linux-next please.

Not a problem.  I'll wait a bit to see what shows up before doing anything.

Regards,
Hartley--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/