linux-kernel - Re: linux-next: Tree for August 28

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]

Message-ID: <20080829081154.GB3387@brain>
Date:	Fri, 29 Aug 2008 09:12:08 +0100
From:	Andy Whitcroft <apw@...dowen.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Takashi Iwai <tiwai@...e.de>
Subject: Re: linux-next: Tree for August 28

On Thu, Aug 28, 2008 at 02:39:34PM -0700, Andrew Morton wrote:
> On Thu, 28 Aug 2008 18:33:07 +1000
> Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> 
> firmware/yamaha/yss225_registers.bin.ihex uses \r\n line termination.
> Is that actually required, or can we use plain old \n?
> 
> Andy, a checkpatch rule for this would be nice.

Ahhh, well we do have a check for DOS line endings, but it only applies
to 'source' files.  I guess what we should do is bring ihex in as a
'text' file format and apply limited checks to that.

-apw
--
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/