From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: "tony@atomide.com" <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Patch "REMOVE OMAP LEGACY CODE: Reset mach-omap1/board-*.c files to mainline" breaks nokia770
Date: Thu, 14 May 2009 03:23:35 +0300 [thread overview]
Message-ID: <20090514002335.GA9538@nokia.com> (raw)
In-Reply-To: <20090514004651.77342rqoq5tz86ww@lidskialf.net>
On Thu, May 14, 2009 at 01:46:51AM +0200, ext Andrew de Quincey wrote:
> Hi, I've just discovered that the patch at:
>
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commitdiff;h=3eae3ea7c443fc4330574dffea65b6f2f53a2574
>
> Breaks the nokia770's framebuffer as it removes the platform data for
> the HWA742 LCD controller.
>
> As the patch says "Patches against the mainline tree are welcome to
> add back the missing functionality if needed!", I'm happy to do this.
>
> However, since I'm fairly new to the linux-omap project, is simply
> extracting the removed nokia770 code and generating a patch against
> the mainline kernel sufficient? or is there a newer style of some sort
> that should be adopted for this?
You can start by generating the new patch against mainline and running
scripts/checkpatch.pl, then you should probably find out if there are
any API changes and stuff like that. Then send the patch to lkml ccing
linux-omap and let's see what comments do you get from those guys :-)
--
balbi
next prev parent reply other threads:[~2009-05-14 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 23:46 Patch "REMOVE OMAP LEGACY CODE: Reset mach-omap1/board-*.c files to mainline" breaks nokia770 Andrew de Quincey
2009-05-14 0:23 ` Felipe Balbi [this message]
2009-05-14 1:44 ` Tony Lindgren
2009-05-14 8:04 ` Felipe Balbi
2009-05-14 15:30 ` Tony Lindgren
2009-05-14 23:18 ` Andrew de Quincey
2009-05-14 23:26 ` Tony Lindgren
2009-05-14 23:37 ` Andrew de Quincey
2009-05-14 23:57 ` Tony Lindgren
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=20090514002335.GA9538@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=adq_dvb@lidskialf.net \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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