Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CAH2r5mvfH2Kn_h2z+NsCoOdN8eBNw9_6=fFmgPvFOejwnCJMuA@mail.gmail.com>
In-Reply-To: <CAH2r5mvfH2Kn_h2z+NsCoOdN8eBNw9_6=fFmgPvFOejwnCJMuA@mail.gmail.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu, 15 Dec 2022 09:32:31 -0800
Message-ID: <CAHk-=wikDs8v=Zk=Tdr7xRO3=9RWRa+2k068Upsk45uSx8r9nw@mail.gmail.com>
Subject: Re: [GIT PULL] ksmbd server fixes
To:     Steve French <smfrench@gmail.com>
Cc:     Namjae Jeon <linkinjeon@kernel.org>,
        CIFS <linux-cifs@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Dec 14, 2022 at 7:18 PM Steve French <smfrench@gmail.com> wrote:
>
> I can also send the client (cifs.ko) P/R tomorrow if it is easier but
> have been working on testing some important fixes which are not in
> linux-next yet, so not sure if it is easier to send the client fixes
> as two P/Rs, or wait and send the client fixes all together as one
> P/R later in the merge window.

I'd like to get the bulk early.

I'm traveling tomorrow (and to make this merge window *extra* fun,
Xfinity was messing with my home network yesterday), so if you have
the first batch that has been in linux-next ready to go, please get
that to me asap.

The less I have to look at while traveling, the better. I'm only on
the road for a couple of days, but then it's xmas week, so...

           Linus