On Fri, Feb 28, 2014 at 10:43:09PM +0100, Paul Bolle wrote:
> That commit is fine with me, of course. I now see no reason to continue
> my, rather slowly progressing, search for the problem that you wanted to
> get properly fixed. I suppose another commit already fixed it.
No, but it's someone
On Wed, 2014-02-12 at 16:04 +, Mark Brown wrote:
> On Mon, Feb 10, 2014 at 11:09:19PM +0100, Paul Bolle wrote:
> > See, if you scan v3.10:arch/arm/mach-exynos/mach-smdkv310.c you'll
> > notice the string "smdk-audio". If you grep that string you get a few
> > hits. But none in
On Wed, 2014-02-12 at 16:04 +, Mark Brown wrote:
On Mon, Feb 10, 2014 at 11:09:19PM +0100, Paul Bolle wrote:
See, if you scan v3.10:arch/arm/mach-exynos/mach-smdkv310.c you'll
notice the string smdk-audio. If you grep that string you get a few
hits. But none in
On Fri, Feb 28, 2014 at 10:43:09PM +0100, Paul Bolle wrote:
That commit is fine with me, of course. I now see no reason to continue
my, rather slowly progressing, search for the problem that you wanted to
get properly fixed. I suppose another commit already fixed it.
No, but it's someone from
On Mon, Feb 10, 2014 at 11:09:19PM +0100, Paul Bolle wrote:
> See, if you scan v3.10:arch/arm/mach-exynos/mach-smdkv310.c you'll
> notice the string "smdk-audio". If you grep that string you get a few
> hits. But none in v3.10:sound/soc/samsung/smdk_wm9713.c. And if you scan
>
On Mon, Feb 10, 2014 at 11:09:19PM +0100, Paul Bolle wrote:
See, if you scan v3.10:arch/arm/mach-exynos/mach-smdkv310.c you'll
notice the string smdk-audio. If you grep that string you get a few
hits. But none in v3.10:sound/soc/samsung/smdk_wm9713.c. And if you scan
On Mon, 2014-02-10 at 16:36 +, Mark Brown wrote:
> On Mon, Feb 10, 2014 at 04:30:42PM +0100, Paul Bolle wrote:
> > So, next step: the Kconfig symbols MACH_SMDKV310 and MACH_SMDKC210 were
> > removed in commit 383ffda2fa ("ARM: EXYNOS: no more support non-DT for
> > EXYNOS SoCs"). That commit
On Mon, Feb 10, 2014 at 04:30:42PM +0100, Paul Bolle wrote:
> On Mon, 2014-02-10 at 14:12 +, Mark Brown wrote:
> > Yes, that's correct. Now, like I say think about what the symbol was
> > there for in the first place.
> So, next step: the Kconfig symbols MACH_SMDKV310 and MACH_SMDKC210 were
On Mon, 2014-02-10 at 14:12 +, Mark Brown wrote:
> On Mon, Feb 10, 2014 at 02:31:12PM +0100, Paul Bolle wrote:
> > 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 ||
On Mon, Feb 10, 2014 at 02:31:12PM +0100, Paul Bolle wrote:
> On Mon, 2014-02-10 at 11:41 +, 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
On Mon, 2014-02-10 at 11:41 +, 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
On Sun, Feb 09, 2014 at 07:47:52PM +0100, Richard Weinberger wrote:
> The symbol is an orphan, get rid of it.
Please fix whatever script you're using to generate your mails, it's
generating corrupt headers. Please also use subject lines consistent
with the rest of the subsystem - between the
On Sun, Feb 09, 2014 at 07:47:52PM +0100, Richard Weinberger wrote:
The symbol is an orphan, get rid of it.
Please fix whatever script you're using to generate your mails, it's
generating corrupt headers. Please also use subject lines consistent
with the rest of the subsystem - between the two
On Mon, 2014-02-10 at 11:41 +, 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
On Mon, Feb 10, 2014 at 02:31:12PM +0100, Paul Bolle wrote:
On Mon, 2014-02-10 at 11:41 +, 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
On Mon, 2014-02-10 at 14:12 +, Mark Brown wrote:
On Mon, Feb 10, 2014 at 02:31:12PM +0100, Paul Bolle wrote:
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
On Mon, Feb 10, 2014 at 04:30:42PM +0100, Paul Bolle wrote:
On Mon, 2014-02-10 at 14:12 +, Mark Brown wrote:
Yes, that's correct. Now, like I say think about what the symbol was
there for in the first place.
So, next step: the Kconfig symbols MACH_SMDKV310 and MACH_SMDKC210 were
On Mon, 2014-02-10 at 16:36 +, Mark Brown wrote:
On Mon, Feb 10, 2014 at 04:30:42PM +0100, Paul Bolle wrote:
So, next step: the Kconfig symbols MACH_SMDKV310 and MACH_SMDKC210 were
removed in commit 383ffda2fa (ARM: EXYNOS: no more support non-DT for
EXYNOS SoCs). That commit was part
18 matches
Mail list logo
