All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Shirish Pargaonkar
	<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: cifs tree updated to back out crypto/ntlmv2/ntlmssp change to 2.6.37 - but now has the cifsd fixes
Date: Thu, 09 Sep 2010 17:31:31 +0530	[thread overview]
Message-ID: <4C88CC9B.9040904@suse.de> (raw)
In-Reply-To: <20100909075242.11d03854-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>

On 09/09/2010 05:22 PM, Jeff Layton wrote:
> On Wed, 8 Sep 2010 16:25:09 -0500
> Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
>> CIFS tree updated to back out the crypto/ntlmv2/ntlmssp change
>> (included patch 2/8 because it was reviewed and independent).   Added
>> to the cifs tree the fixes to prevent premature exit to cifsd and to
>> prevent the possibly ip address memory corruption.
>>
>> -- 
>> Thanks,
>>
> 
> Looks good to me.
> 
> BTW, when you send the pull request to Linus, could you also cc
> linux-cifs? It's helpful to know when you send these out so that we know
> to keep a closer eye on mainline.
> 

Yes, please. It would help to know when pull request is being sent.

Thanks,

-- 
Suresh Jayaraman

  parent reply	other threads:[~2010-09-09 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 21:25 cifs tree updated to back out crypto/ntlmv2/ntlmssp change to 2.6.37 - but now has the cifsd fixes Steve French
     [not found] ` <AANLkTimraXF9gVC-o5qb2mfDfrq6=9-CTtyGeew27ne6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-09 11:52   ` Jeff Layton
     [not found]     ` <20100909075242.11d03854-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2010-09-09 12:01       ` Suresh Jayaraman [this message]
     [not found]         ` <4C88CC9B.9040904-l3A5Bk7waGM@public.gmane.org>
2010-09-09 15:34           ` Steve French

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C88CC9B.9040904@suse.de \
    --to=sjayaraman-l3a5bk7wagm@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.