From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Thomas Weber <thomas.weber.linux@googlemail.com>,
"Nori, Sekhar" <nsekhar@ti.com>,
Thomas Weber <weber@corscience.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC/PATCH] ARM: OMAP: Fix build for OMAP3 only builds
Date: Mon, 7 Nov 2011 09:29:41 -0800 [thread overview]
Message-ID: <20111107172940.GT31337@atomide.com> (raw)
In-Reply-To: <20111107170608.GD15294@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [111107 08:31]:
> On Thu, Nov 03, 2011 at 11:30:02AM -0700, Tony Lindgren wrote:
> > Considering we now have the DT branch merged, I'll apply the earlier
> > patch from Sanjeev with a minor modification to avoid a build
> > warning in board-generic.c.
> >
> > Updated patch below, Sekhar & Thomas, care to ack?
>
> When are we likely to see this patch in mainline given that my OMAP
> builds are yet again broken during the merge window?
This is queud in fixes branch now.
> (You can *and should* send fixes for regressions during the merge window.
> If you want to batch them up and send them towards the end of the merge
> window, that's a good idea too. But to have a broken -rc1 is bad
> practice.)
Right, sorry for the delays. I think I have all the pending fixes
now queued finally.
Regards,
Tony
next prev parent reply other threads:[~2011-11-07 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 12:03 [RFC/PATCH] ARM: OMAP: Fix build for OMAP3 only builds Thomas Weber
2011-10-27 5:32 ` Nori, Sekhar
2011-11-02 12:37 ` Thomas Weber
2011-11-02 17:16 ` Tony Lindgren
2011-11-03 18:30 ` Tony Lindgren
2011-11-03 21:24 ` Thomas Weber
2011-11-07 17:06 ` Russell King - ARM Linux
2011-11-07 17:29 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-29 4:42 Thomas Weber
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=20111107172940.GT31337@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.com \
--cc=thomas.weber.linux@googlemail.com \
--cc=weber@corscience.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox