public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: Linux OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH 1/2] OMAP: Kill compile warnings
Date: Tue, 5 Jun 2007 03:21:14 -0700	[thread overview]
Message-ID: <20070605102114.GD859@atomide.com> (raw)
In-Reply-To: <20070605101132.GC859@atomide.com>

* Tony Lindgren <tony@atomide.com> [070605 03:16]:
> * Dirk Behme <dirk.behme@googlemail.com> [070525 23:02]:
> > Syed Mohammed, Khasim wrote:
> >>> That would be redundant:
> >>> 220         /* Get the debug Device */
> >>> 221         dbg_dev = &(pdev->dev);
> >>> already did that for you.. only, now the messages will show
> >>> "input:xyz.." instead of "omap_twl4030:xyz"..
> >> OK, thanks. Acked-by: x0khasim@ti.com
> >
> > Okay, after 2 minutes thinking about what's so confusing here, I have
> > it now. We have two different patches with nearly identical subject.
> > The first one should fix a warning we already discussed under an other
> > subject. A answer to the second patch was sent under the subject of
> > the first one ;) Therefore some clarification as I understand it now:
> >
> > We have two warnings:
> >
> > 1) Section mismatch with sys_timer
> >
> > This is what "[PATCH 1/2] OMAP: Kill compile warnings" is about.
> >
> > As mentioned by Tony this patch isn't correct and we will wait (as
> > discussed already earlier) until this is fixed by ignore list.
> >
> > http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/010087.html
> >
> > http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/010061.html
> >
> > 2) Warning in twl4030 keypad about dbg_dev
> >
> > This is what "[PATCH 2/2] OMAP: Kill compile warnings" is about.
> >
> > For this we already had an other subject in the list archives as well
> > "Compiler warning in omap-twl4030keypad.c".
> >
> > Above Khasim acked it (with misleading subject ;) ) and I also think
> > it's okay
> >
> > http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/010086.html
> >
> > Acked-by: Dirk Behme <dirk.behme@gmail.com>
> >
> > Conclusion: For (1) we have to wait, for (2) please apply.
> >
> > Hope that helps a little,
> 
> Yeah, it's getting complex :) Pushing Felipe's patch posted by Nishant
> today.

Correction Felipe's patch posted by Khasim :)

Tony

      reply	other threads:[~2007-06-05 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 23:04 [PATCH 1/2] OMAP: Kill compile warnings nishanth menon
2007-05-25 23:12 ` Tony Lindgren
2007-05-25 23:17   ` Syed Mohammed, Khasim
2007-05-25 23:23     ` nishanth menon
2007-05-25 23:25       ` Syed Mohammed, Khasim
2007-05-26  5:38         ` Dirk Behme
2007-06-05 10:11           ` Tony Lindgren
2007-06-05 10:21             ` 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=20070605102114.GD859@atomide.com \
    --to=tony@atomide.com \
    --cc=dirk.behme@googlemail.com \
    --cc=linux-omap-open-source@linux.omap.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