All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Omar Ramirez Luna <omar.ramirez@ti.com>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH 1/5] omap: OMAP_DSP is not in mainline, remove it
Date: Mon, 5 Jul 2010 12:29:49 +0300	[thread overview]
Message-ID: <20100705092947.GN15951@atomide.com> (raw)
In-Reply-To: <1278250586-17062-2-git-send-email-felipe.contreras@gmail.com>

* Felipe Contreras <felipe.contreras@gmail.com> [100704 16:30]:
> Cc: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>

Missing description, maybe check your other patches for that too.
Anyways, I've queued up an earlier similar patch from
Christoph Egger <siccegge@cs.fau.de>:

https://patchwork.kernel.org/patch/110186/

Regards,

Tony


  reply	other threads:[~2010-07-05  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-04 13:36 [PATCH 0/5] staging: ti dspbridge: improve Kconfig Felipe Contreras
2010-07-04 13:36 ` [PATCH 1/5] omap: OMAP_DSP is not in mainline, remove it Felipe Contreras
2010-07-05  9:29   ` Tony Lindgren [this message]
2010-07-04 13:36 ` [PATCH 2/5] staging: ti dspbridge: prefix configs with TIDSPBRIDGE Felipe Contreras
2010-07-04 13:36 ` [PATCH 3/5] staging: ti dspbridge: improve Kconfig Felipe Contreras
2010-07-04 13:36 ` [PATCH 4/5] staging: ti dspbridge: use _DEBUG for debug trace Felipe Contreras
2010-07-04 13:36 ` [PATCH 5/5] staging: ti dspbridge: add _BACKTRACE config Felipe Contreras
  -- strict thread matches above, loose matches on Subject: below --
2010-05-16 15:46 [PATCH 0/8] dspbridge: improve Kconfig Felipe Contreras
2010-05-16 15:46 ` [PATCH 1/5] omap: OMAP_DSP is not in mainline, remove it Felipe Contreras

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=20100705092947.GN15951@atomide.com \
    --to=tony@atomide.com \
    --cc=felipe.contreras@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=omar.ramirez@ti.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.