From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Russell King <rmk@arm.linux.org.uk>,
kernel list <linux-kernel@vger.kernel.org>,
vovan888@gmail.com
Subject: Re: Protocol for merging -omap changes
Date: Fri, 27 Oct 2006 18:54:10 +0300 [thread overview]
Message-ID: <20061027155408.GE25245@atomide.com> (raw)
In-Reply-To: <20061027124250.GA30311@elf.ucw.cz>
Hi,
* Pavel Machek <pavel@ucw.cz> [061027 15:43]:
> Hi!
>
> I see that linux-omap still has pretty big difference from
> linux-arm... are there any plans at merging them? Is there some way I
> could help?
Yeah, let's get more of the commonly used omap drivers merged!
> I have bunch of siemens sx1 changes from Vladimir here, and some of
> them seem ready to merge... should they be merged with Tony? Or
> directly with rmk bringing stuff from -omap tree as needed?
Core omap stuff goes first to linux-omap tree, and then gets merged
to mainline kernel through RMK. Drivers should go through the
appropriate driver maintainers or LKML.
So please split your patches accordingly. All arch/arm/*omap* and
include/asm-arm/arch-omap patches should be separate from drivers.
Regards,
Tony
prev parent reply other threads:[~2006-10-27 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 12:42 Protocol for merging -omap changes Pavel Machek
2006-10-27 15:54 ` Tony Lindgren [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=20061027155408.GE25245@atomide.com \
--to=tony@atomide.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rmk@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox