All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
	Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>,
	alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
	Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Hugo Villeneuve <hugo-rg2e/+w5TaNBDgjK7y7TUQ@public.gmane.org>,
	Jaroslav Kysela <perex-/Fr2/VpizcU@public.gmane.org>
Subject: Re: [PATCH] sound/soc/davinci: remove sffsdr machine support
Date: Mon, 17 Jun 2013 14:47:46 +0530	[thread overview]
Message-ID: <51BED43A.3030608@ti.com> (raw)
In-Reply-To: <20130617090524.GW1403-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>

Mark,

On 6/17/2013 2:35 PM, Mark Brown wrote:
> On Mon, Jun 17, 2013 at 02:16:31PM +0530, Sekhar Nori wrote:
>> sffsdr machine support does not build since at least v2.6.36
>> (~3 years). There is little hope of it being fixed, so remove
>> the support.
> 
> This doesn't actually apply against -next and I had to fix up the
> subject line too but applied anyway, thanks.

Thanks for applying. I looked at wrong examples of subject line
convention in git log. The ones I looked at turned out to be merged from
outside of ASoC tree. Sigh.

Thanks,
Sekhar

      parent reply	other threads:[~2013-06-17  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  8:46 [PATCH] sound/soc/davinci: remove sffsdr machine support Sekhar Nori
     [not found] ` <1371458791-7530-1-git-send-email-nsekhar-l0cyMroinI0@public.gmane.org>
2013-06-17  9:05   ` Mark Brown
     [not found]     ` <20130617090524.GW1403-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-06-17  9:17       ` Sekhar Nori [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=51BED43A.3030608@ti.com \
    --to=nsekhar-l0cymroini0@public.gmane.org \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
    --cc=hugo-rg2e/+w5TaNBDgjK7y7TUQ@public.gmane.org \
    --cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=perex-/Fr2/VpizcU@public.gmane.org \
    --cc=tiwai-l3A5Bk7waGM@public.gmane.org \
    /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.