From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Omar Ramirez Luna <omar.ramirez@copitl.com>
Cc: Victor Manuel Jaquez Leal <vjaquez@igalia.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] staging: tidspbridge fixes for 3.7
Date: Wed, 24 Oct 2012 16:35:55 -0700 [thread overview]
Message-ID: <20121024233555.GA13874@kroah.com> (raw)
In-Reply-To: <CAJ6Av5O0Ri-ZzNj-MnFH53qSdc9r_BNCVs=ktRY5+qUqEzGaGA@mail.gmail.com>
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@linuxfoundation.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
prev parent reply other threads:[~2012-10-24 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 22:09 [PATCH 0/6] staging: tidspbridge fixes for 3.7 Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 1/6] staging: tidspbridge: request the right irq for mmu Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 2/6] staging: tidspbridge: drop const from custom mmu implementation Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 3/6] staging: tidspbridge: change type to __iomem for per and core addresses Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 4/6] staging: tidspbridge: ioremap dsp sync addr Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 5/6] staging: tidspbridge: ioremap physical address of the stack segment in shm Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 6/6] staging: tidspbridge: delete unused mmu functions Omar Ramirez Luna
2012-10-24 22:28 ` [PATCH 0/6] staging: tidspbridge fixes for 3.7 Greg Kroah-Hartman
2012-10-24 23:25 ` Omar Ramirez Luna
2012-10-24 23:35 ` Greg Kroah-Hartman [this message]
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=20121024233555.GA13874@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.ramirez@copitl.com \
--cc=vjaquez@igalia.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.