linux-kernel - Re: [PATCH v3] USB: mos7720: rename registers

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:	Fri, 26 Jun 2015 19:23:23 +0530
From:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
To:	Johan Hovold <johan@...nel.org>,
	David Howells <dhowells@...hat.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-am33-list@...hat.com, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: [PATCH v3] USB: mos7720: rename registers

On Fri, Jun 26, 2015 at 09:46:43AM +0200, Johan Hovold wrote:
> On Tue, Jun 23, 2015 at 06:59:40PM +0530, Sudip Mukherjee wrote:
> > Some of the register names defined here are matching with registers
> > defined in other places. Like DCR is defined here and DCR is also
> > a register in mn10300 architecture. So when we are building this with
> > mn10300, build fails.
> > To avoid we rename all the registers.
> > 
> > Signed-off-by: Sudip Mukherjee <sudip@...torindia.org>
> 
> Looks good. I'll queue this up for 4.2.
Thanks Johan.

David,
This series works on next-20150618. But next-20150625 again fails in
allmodconfig of mn10300. I did a bisect and the first bad commit is:
db8786a2829c ("Merge remote-tracking branch 'dt-rh/for-next'").
And reverting it solved the problem. I will find out what was the exact
problem in that merge, but after I find out should i send a new series
or another patch?

regards
sudip

--
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/