From: Tony Lindgren <tony@atomide.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: Linux OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH 1/2] [OMAP MMU FWK] Translate printk to dev_* and break lines with more than 80 char
Date: Mon, 17 Sep 2007 11:07:31 -0700 [thread overview]
Message-ID: <20070917180730.GB21226@atomide.com> (raw)
In-Reply-To: <a0580c510709141018r7e673cd5r3eb22b7627f4618e@mail.gmail.com>
* Eduardo Valentin <edubezval@gmail.com> [070914 10:19]:
> Hi Dirk,
>
>
> Yes, the patch I sent last month is outdated. But this new one has
> just little differences. I resent it as the last one was not merged
> and the second on the series is on top of this.
Pushing both of these today.
Tony
prev parent reply other threads:[~2007-09-17 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11897112792637-git-send-email-edubezval@gmail.com>
2007-09-13 19:21 ` [PATCH 1/2] [OMAP MMU FWK] Translate printk to dev_* and break lines with more than 80 char Eduardo Valentin
2007-09-13 19:21 ` [PATCH 2/2] [OMAP MMU FWK] Improve debug messages and removed DSP references from MMU FW code Eduardo Valentin
2007-09-14 16:38 ` [PATCH 1/2] [OMAP MMU FWK] Translate printk to dev_* and break lines with more than 80 char Dirk Behme
2007-09-14 17:18 ` Eduardo Valentin
2007-09-17 18:07 ` 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=20070917180730.GB21226@atomide.com \
--to=tony@atomide.com \
--cc=edubezval@gmail.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