archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <>
To: Stephen Rothwell <>
	Tomi Valkeinen <>
Subject: Re: linux-next: manual merge of the moduleh tree with Linus' tree
Date: Tue, 2 Aug 2011 13:17:49 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Aug 2, 2011 at 12:52 AM, Stephen Rothwell <> wrote:
> Hi Paul,
> Today's linux-next merge of the moduleh tree got a conflict in
> drivers/video/omap2/dss/rfbi.c between commit 24e6289c029b ("OMAP: DSS2:
> remove extra includes from include/video/omapdss.h") from Linus' tree and
> commit 06e632e042aa ("video: Add export.h for THIS_MODULE/EXPORT_SYMBOL
> to drivers/video") from the moduleh tree.
> Just overlapping additions.  I fixed it up (see below) and can carry the
> fix as necessary.

I was making some cosmetic changes to commit logs (such as adding Acked-by
etc) and so took the opportunity to just relocate the export.h
addition up higher
and out of the way, which should make this go away for you/Linus.

Thanks for the heads up,

> --
> Cheers,
> Stephen Rothwell          
> diff --cc drivers/video/omap2/dss/rfbi.c
> index 39f4c59,5dbd229..0000000
> --- a/drivers/video/omap2/dss/rfbi.c
> +++ b/drivers/video/omap2/dss/rfbi.c
> @@@ -33,8 -33,7 +33,9 @@@
>  #include <linux/hrtimer.h>
>  #include <linux/seq_file.h>
>  #include <linux/semaphore.h>
>  +#include <linux/platform_device.h>
>  +#include <linux/pm_runtime.h>
> + #include <linux/export.h>
>  #include <video/omapdss.h>
>  #include "dss.h"
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to
> More majordomo info at
> Please read the FAQ at

  reply	other threads:[~2011-08-02 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02  4:52 linux-next: manual merge of the moduleh tree with Linus' tree Stephen Rothwell
2011-08-02 17:17 ` Paul Gortmaker [this message]
2011-09-28  6:20 Stephen Rothwell
2011-10-25  8:37 Stephen Rothwell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).