All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Komal Shah <komal.shah802003@gmail.com>,
	Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	Vladimir Ananiev <vovan888@gmail.com>
Subject: Re: omap compilation fixes
Date: Fri, 22 Dec 2006 11:51:16 -0800	[thread overview]
Message-ID: <20061222195115.GC2449@atomide.com> (raw)
In-Reply-To: <20061222115116.GA961@flint.arm.linux.org.uk>

Hi,

* Russell King <rmk+lkml@arm.linux.org.uk> [061222 03:51]:
> On Fri, Dec 22, 2006 at 01:35:31PM +0200, Komal Shah wrote:
> > On 12/22/06, Pavel Machek <pavel@ucw.cz> wrote:
> > >Hi!
> > >
> > >This is not yet complete set. set_map() is missing in latest kernels.
> > >
> > >Fix DECLARE_WORK()-change-related compilation problems. Please apply,
> > >
> > >Signed-off-by: Pavel Machek <pavel@suse.cz>
> > >
> > 
> > Please check linux-omap-open-source mailing list. Some of the build
> > breakage patches are already posted regarding to latest kernel sync
> > up.
> > 
> > http://linux.omap.com/pipermail/linux-omap-open-source
> 
> There are a set of omap patches in the patch system, but they were too
> late for me to merge within the 2 week window - there were additional
> delays caused by the accidental attempt to merge the silly ATAG_BOARD
> stuff which I had previously refused.
> 
> Tony needs to either create a git tree containing strictly just fixes
> suitable for -rc kernels, or submit them as individual patches.

Yeah, I'll put together a set of fixes shortly, and will keep the
larger merge set for post 2.6.20.

Regards,

Tony

  reply	other threads:[~2006-12-22 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22 10:55 omap compilation fixes Pavel Machek
2006-12-22 11:35 ` Komal Shah
2006-12-22 11:51   ` Russell King
2006-12-22 19:51     ` Tony Lindgren [this message]
2006-12-22 21:17 ` Tony Lindgren
2006-12-22 21:48   ` Pavel Machek
2006-12-23 19:48     ` Tony Lindgren
2006-12-26 14:22       ` Pavel Machek

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=20061222195115.GC2449@atomide.com \
    --to=tony@atomide.com \
    --cc=komal.shah802003@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=vovan888@gmail.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.