linux-kernel - Re: ath5k text

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: <20080818.000513.224752343.davem@davemloft.net>
Date:	Mon, 18 Aug 2008 00:05:13 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jirislaby@...il.com
Cc:	linville@...driver.com, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel@...rcher.dialup.fu-berlin.de
Subject: Re: ath5k text

From: Jiri Slaby <jirislaby@...il.com>
Date: Mon, 18 Aug 2008 09:00:34 +0200

> On 08/18/2008 12:12 AM, David Miller wrote:
> > Their commit messages reference SHA IDs but do not give a commit
> > header line text reference as well.
> > 
> >       ath5k: Don't fiddle with MSI on suspend/resume.
> 
> John, this is it (even if I don't understand the purpose):

The purpose is that when patches are backported or moved to
other GIT trees, the SHA ID is going to be different.

So when you reference just the SHA ID it is not enough
infomration to universally find the commit you are referring
to.

Do you understand "the purpose" now? :-)

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