This patch was posted a week ago and still is not in the upstream tree. Typically Joel waits for sometime to collect patches before pushing them upstream. On 04/12/2011 09:14 AM, Ian B. MacDonald wrote:> Sunil, > > Quick question, > > Is there an easy way to find this patch in upstream kernel/git? i > browsed the changelog for 2.6.39-rcX .. lots of ocfs2 stuff, but I > didn't see specific reference to this patch set. > > Is that because it is still under review? > > cheers, > Ian > > On Mon, 2011-04-11 at 12:25 -0700, Sunil Mushran wrote: >> No bug was filed. ocfs2-users has mail thread regarding this issue. But you are welcome to file one on oss bz and use it for tracking purposes. >> >> On Apr 11, 2011, at 10:40 AM, "Ian B. MacDonald"<ian.macdonald at n8id.com> wrote: >> >>> Sunil, >>> >>> I am looking to find the upstream bug reference for the patches in the >>> thread below, so I can link them properly to a distribution bug report >>> to have them backported to current 2.6.37 packages. >>> >>> http://oss.oracle.com/pipermail/ocfs2-devel/2011-April/007996.html >>> >>> Can you please provide the oss.oracle.com bug reference for the o2dlm >>> protocol identification bug described here. I tried my hand at the >>> advanced search in bugzilla with no luck. >>> >>> Much appreciated, >>> >>> thanks, >>> Ian >>> >>> >>> -- >>> Ian B. MacDonald >>> Director of Product Management >>> N8 Identity Inc. >>> W:(416)800-2209 >>> M:(416)988-0856 >>> >>> -- >>> This e-mail may be privileged and/or confidential, and the sender does >>> not waive any related rights and obligations. Any distribution, use or >>> copying of this e-mail or the information it contains by other than an >>> intended recipient is unauthorized. If you received this e-mail in >>> error, please advise me (by return e-mail or otherwise) immediately. >>> >>> Ce courriel peut contenir des renseignements prot?g?s et confidentiels. >>> L'exp?diteur ne renonce pas aux droits et obligations qui s'y >>> rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des >>> renseignements qu'il contient par une personne autre que le destinataire >>> d?sign? est interdite. Si vous recevez ce courriel par erreur, veuillez >>> m'en aviser imm?diatement, par retour de courriel ou par un autre moyen. >>>