linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 14/28] Remove MACH_SMDKC210
Date: Mon, 10 Feb 2014 14:31:12 +0100	[thread overview]
Message-ID: <1392039072.3585.15.camel@x220> (raw)
In-Reply-To: <20140210114154.GQ1757@sirena.org.uk>

On Mon, 2014-02-10 at 11:41 +0000, Mark Brown wrote:
> On Sun, Feb 09, 2014 at 07:47:52PM +0100, Richard Weinberger wrote:
> Please fix whatever script you're using to generate your mails, it's
> generating corrupt headers.

I think Richard's mail didn't end up on lkml. But it's pretty clear what
it must have looked like.

> >  config SND_SOC_SAMSUNG_SMDK_WM9713
> >  	tristate "SoC AC97 Audio support for SMDK with WM9713"
> > -	depends on SND_SOC_SAMSUNG && (MACH_SMDK6410 || MACH_SMDKC100 || MACH_SMDKV210 || MACH_SMDKC110 || MACH_SMDKV310 || MACH_SMDKC210)
> > +	depends on SND_SOC_SAMSUNG && (MACH_SMDK6410 || MACH_SMDKC100 || MACH_SMDKV210 || MACH_SMDKC110 || MACH_SMDKV310)
> 
> Like I said to Paul this isn't fixing the actual issue - think about why
> the symbol was there in the first place and why it was removed.  There
> is a problem here but this would make it less likely that it would be
> properly fixed.

Would you mind going through this one step at a time, just to make sure
_I_ understand what it is that you'd like to see?

If so, to be absolutely sure we start from the same point: do you agree
that the above line now effectively reads
    depends on SND_SOC_SAMSUNG && (MACH_SMDK6410 || MACH_SMDKC100 || MACH_SMDKV210 || MACH_SMDKC110 || false || false)

because there's neither a Kconfig symbol MACH_SMDKV310 nor a Kconfig
symbol MACH_SMDKC210?


Paul Bolle

  reply	other threads:[~2014-02-10 13:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1391971686-9517-1-git-send-email-richard@nod.at>
2014-02-09 18:47 ` [PATCH 12/28] Remove GENERIC_TIME Richard Weinberger
2014-02-09 18:57   ` Alexander Shiyan
2014-02-09 20:02     ` Richard Weinberger
2014-02-19  6:12       ` Christian Daudt
2014-02-09 18:47 ` [PATCH 13/28] Remove S3C24XX_GPIO_EXTRA64 Richard Weinberger
2014-02-11  3:29   ` Kukjin Kim
2014-02-09 18:47 ` [PATCH 14/28] Remove MACH_SMDKC210 Richard Weinberger
2014-02-10 11:41   ` Mark Brown
2014-02-10 13:31     ` Paul Bolle [this message]
2014-02-10 14:12       ` Mark Brown
2014-02-10 15:30         ` Paul Bolle
2014-02-10 16:36           ` Mark Brown
2014-02-10 22:09             ` Paul Bolle
2014-02-12 16:04               ` Mark Brown
2014-02-28 21:43                 ` Paul Bolle
2014-03-01  3:53                   ` Mark Brown
2014-02-09 18:48 ` [PATCH 22/28] Remove S3C24XX_GPIO_EXTRA128 Richard Weinberger
2014-02-11  3:31   ` Kukjin Kim
2014-02-13 22:57     ` Kukjin Kim
2014-02-09 18:48 ` [PATCH 25/28] Remove MACH_SMDKV310 Richard Weinberger
2014-02-09 18:48 ` [PATCH 26/28] Remove LOCAL_TIMERS Richard Weinberger
2014-02-09 22:38   ` Paul Bolle
2014-02-09 18:48 ` [PATCH 28/28] " Richard Weinberger
2014-02-09 22:49   ` Paul Bolle
     [not found] ` <1391971686-9517-7-git-send-email-richard@nod.at>
     [not found]   ` <1391977683.25855.27.camel@x220>
2014-04-15  8:55     ` [PATCH] hwrng: remove unbuildable picoxcell TRNG Paul Bolle
2014-04-15 10:06       ` Jamie Iles
2014-04-16 13:50         ` Herbert Xu

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=1392039072.3585.15.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).