Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754495AbYHAPYR (ORCPT ); Fri, 1 Aug 2008 11:24:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751530AbYHAPYB (ORCPT ); Fri, 1 Aug 2008 11:24:01 -0400 Received: from wf-out-1314.google.com ([209.85.200.168]:13815 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751247AbYHAPYA (ORCPT ); Fri, 1 Aug 2008 11:24:00 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=rICkK0ymDOlObvk6inGNokJQKmw4A9dvHkzaPk/+kWezCZRLla0G5yPTa7BFBnVeOO xAtJOhEqwzIYGlInMT6SLytnHa5f8jMRt5ke54pNF+JHJsCu17SN4Gj9nNESr7/lnBoL XzzaDGJhX4glvFm3Cpd4//+v2KyCFAIKvpRfo= Message-ID: Date: Fri, 1 Aug 2008 11:23:59 -0400 From: "Bob Copeland" To: "Jiri Slaby" Subject: Re: [PATCH] ath5k : ath5k_config_interface deadlock fix Cc: "Andrew Morton" , "Pekka Enberg" , "Dave Young" , johannes@sipsolutions.net, tomasw@gmail.com, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, ath5k-devel@venema.h4ckr.net, linville@tuxdriver.com, stable@kernel.org In-Reply-To: <4893257C.1020907@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080801074014.GA3341@darkstar> <4892C2CA.7010003@gmail.com> <4892C359.9000304@cs.helsinki.fi> <20080801011415.ff4821a3.akpm@linux-foundation.org> <4893257C.1020907@gmail.com> X-Google-Sender-Auth: 1198bb72ac406d57 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 949 Lines: 24 On Fri, Aug 1, 2008 at 11:02 AM, Jiri Slaby wrote: >> >> Not to worry, the commit that introduced it was >> 9d139c810a2aa17365cc548d0cd2a189d8433c65, which as far as I can tell >> came in after 2.6.26. > > git-describe 9d139c810a2aa17365cc548d0cd2a189d8433c65 > v2.6.26-rc8-1219-g9d139c8 I'm not that expert in git, what does that mean? Some other commits for 2.6.27 also show a 2.6.26-rc from git-describe (e.g. my 3a078876caee). For my own investigation, I did a 'git-checkout v2.6.26' and looked at the code to see the patch had not been applied yet. Is there an easier way to definitively say commit X is/is not in tagged release Y? -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/