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: <84144f020803221557t36502f6bo327c95705be706bf@mail.gmail.com>
Date:	Sun, 23 Mar 2008 00:57:29 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"David Miller" <davem@...emloft.net>
Cc:	jesper.juhl@...il.com, chrisw@...s-sol.org,
	linux-kernel@...r.kernel.org, stable@...nel.org,
	jmforbes@...uxtx.org, zwane@....linux.org.uk, tytso@....edu,
	rdunlap@...otime.net, davej@...hat.com, chuckw@...ntumlinux.com,
	reviews@...cw.f00f.org, mkrufky@...uxtv.org, cebbert@...hat.com,
	cavokz@...il.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, gregkh@...e.de
Subject: Re: [patch 07/76] NIU: Bump driver version and release date.

Hi David,

On Sat, Mar 22, 2008 at 2:14 AM, David Miller <davem@...emloft.net> wrote:
>  It makes a difference for driver maintainers when users
>  report bugs and we ask them for the version printed
>  by the driver so that we know which fixes have been
>  applied.
>
>  You know, if people are going to be jerky about this,
>  I'll just include the version bump in the actual bug
>  fixes which I sometimes do anyways.
>
>  Thanks for bringing this up, it's a useful use of
>  everyone's time :-/

Uhm, Jesper was asking a relevant question and definitely not being
"jerky". As you probably know, many of us are dropping explicit driver
versions from the code for the exact reason why you're trying to patch
the stable tree now. They get out of sync real easy and the kernel
version already provides the same information so why bother.

Furthermore, I honestly don't see how your patch meets the (rather
strict) requirements of stable series either. So it would be nice if
one of the stable maintainers stepped up to say that these kind of
patches are okay to set a precedent for others as well.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ