linux-kernel - Re: [PATCH 0/6] staging: tidspbridge fixes for 3.7

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] [day] [month] [year] [list]

Date:	Wed, 24 Oct 2012 16:35:55 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Omar Ramirez Luna <omar.ramirez@...itl.com>
Cc:	Victor Manuel Jaquez Leal <vjaquez@...lia.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] staging: tidspbridge fixes for 3.7

On Wed, Oct 24, 2012 at 06:25:42PM -0500, Omar Ramirez Luna wrote:
> Hi,
> 
> On Wed, Oct 24, 2012 at 5:28 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > On Wed, Oct 24, 2012 at 05:09:14PM -0500, Omar Ramirez Luna wrote:
> >> With 3.7-rc1 changes:
> >>
> >> - New irq numbering in OMAP3 broke the driver request for a mmu irq,
> >>   until this is migrated to the common iommu framework we can only
> >>   hardcode the new number.
> >> - _raw_* accessors changed a type of one of their parameters with patch
> >>   "195bbca ARM: 7500/1: io: avoid writeback addressing modes for
> >>   __raw_ accessors", so the build system was filled with warnings from
> >>   the old parameter usage.
> >>
> >> Omar Ramirez Luna (6):
> >>   staging: tidspbridge: request the right irq for mmu
> >>   staging: tidspbridge: drop const from custom mmu implementation
> >>   staging: tidspbridge: change type to __iomem for per and core
> >>     addresses
> >>   staging: tidspbridge: ioremap dsp sync addr
> >>   staging: tidspbridge: ioremap physical address of the stack segment
> >>     in shm
> >>   staging: tidspbridge: delete unused mmu functions
> >
> > Are the "fix up the compiler warning" patches really needed for 3.7?
> > Are they new in 3.7-rc1?  Or were they there before in 3.6?
> 
> All are new in 3.7-rc1.
> 
> The "warning fixes" would be good to have and thought they could make
> it given that the change was introduced during 3.7 rc cycle. So, the
> warnings are not that critical.

Ok, good enough, I'll queue this up for 3.7.

greg k-h
--
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/