linux-kernel - Re: [PATCH] sound: max98090: Remove executable bit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Mar 2013 10:53:13 -0700
From:	Joe Perches <joe@...ches.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sound: max98090: Remove executable bit

On Thu, 2013-03-21 at 18:44 +0100, Mark Brown wrote:
> On Thu, Mar 21, 2013 at 10:16:15AM -0700, Joe Perches wrote:
> > On Thu, 2013-03-21 at 17:25 +0100, Mark Brown wrote:
> 
> > > I don't think you're quite understanding the issues with automation
> > > here.  Or indeed the desired end result.
> 
> > What issue is that?
> 
> That one needs a bit more taste and thought to work out what's
> appropraite than can be guaranteed easily with a script, things like
> working out drive level prefixes for example.

[perfectly useful git applypatch-msg hook script removed]

> No, that's going to leave essentially every commit that needs fixing up
> still needing manual fixup.

Then I'm sure that's your job as a maintainer
to modify whatever patches you get to suit your
taste.

I think what I did is perfectly tasty.

ttfn, o+o, ttyl, tafn, etc...

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/