All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "me@felipebalbi.com" <me@felipebalbi.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"felipe.balbi@nokia.com" <felipe.balbi@nokia.com>,
	tony@atomide.com
Subject: Re: [PATCH] watchdog: fix typo in omap_wdt.c
Date: Mon, 29 Sep 2008 12:25:29 +0300	[thread overview]
Message-ID: <20080929092528.GE30555@frodo> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB02D5DC9707@dbde02.ent.ti.com>

On Mon, Sep 29, 2008 at 09:56:06AM +0530, Gadiyar, Anand wrote:
> <snip> 
> 
> > > > Those patches weren't applied to linux-omap yet, so this change should
> > > > be melded into the patch that introduced it. It's better to resend that
> > > > patch then to create a messed up bisect line.
> > > > 
> > > > -- 
> > > > balbi
> > > 
> > > Of course they were merged. I saw this warning when I compiled linux-omap,
> > > when sending in that pin-muxing patch.
> > 
> > You're right, at first look I thought this was for omap_hdq.c :-p
> > 
> > Anyways, this patch should go also to Wim. Please send a copy of this
> > patch to him so he can apply to his tree as well, btw, here's 
> > his mail:
> > 
> > Wim Van Sebroeck <wim@iguana.be>
> > 
> 
> Done. I'm guessing I don't need to CC linux-omap on that. Let me know if
> I should have. I've sent it to Wim, with a CC to you (Felipe).

I think you can send it to l-o so we avoid these kinds of bugs. Tony,
what do you say ?

-- 
balbi

  reply	other threads:[~2008-09-29  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 15:50 [PATCH] watchdog: fix typo in omap_wdt.c Gadiyar, Anand
2008-09-26 17:52 ` Felipe Balbi
2008-09-26 18:02   ` Gadiyar, Anand
2008-09-26 19:27     ` Felipe Balbi
2008-09-29  4:26       ` Gadiyar, Anand
2008-09-29  9:25         ` Felipe Balbi [this message]
2008-09-29  9:29           ` Gadiyar, Anand

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=20080929092528.GE30555@frodo \
    --to=me@felipebalbi.com \
    --cc=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --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 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.