From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steve French <smfrench@gmail.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
CIFS <linux-cifs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] ksmbd server fixes
Date: Thu, 15 Dec 2022 09:32:31 -0800 [thread overview]
Message-ID: <CAHk-=wikDs8v=Zk=Tdr7xRO3=9RWRa+2k068Upsk45uSx8r9nw@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5mvfH2Kn_h2z+NsCoOdN8eBNw9_6=fFmgPvFOejwnCJMuA@mail.gmail.com>
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
next prev parent reply other threads:[~2022-12-15 17:32 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 3:18 [GIT PULL] ksmbd server fixes Steve French
2022-12-15 17:32 ` Linus Torvalds [this message]
2022-12-15 18:28 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-04-22 23:20 Steve French
2024-04-22 23:51 ` pr-tracker-bot
2024-04-05 3:15 Steve French
2024-04-05 17:09 ` pr-tracker-bot
2024-03-20 17:06 Steve French
2024-03-20 23:46 ` pr-tracker-bot
2024-02-10 1:45 Steve French
2024-02-10 16:26 ` pr-tracker-bot
2024-01-27 7:20 Steve French
2024-01-27 17:21 ` pr-tracker-bot
2024-01-18 0:39 Steve French
2024-01-19 18:03 ` pr-tracker-bot
2024-01-11 14:20 Steve French
2024-01-12 5:07 ` pr-tracker-bot
2023-11-27 21:00 Steve French
2023-11-28 1:26 ` pr-tracker-bot
2023-11-10 7:16 Steve French
2023-11-10 18:47 ` pr-tracker-bot
2023-11-02 2:46 Steve French
2023-11-02 18:38 ` pr-tracker-bot
2023-10-15 2:46 Steve French
2023-10-15 2:52 ` pr-tracker-bot
2023-10-08 4:27 Steve French
2023-10-08 18:06 ` pr-tracker-bot
2023-09-17 1:55 Steve French
2023-09-17 18:24 ` pr-tracker-bot
2023-08-09 23:11 Steve French
2023-08-10 5:02 ` pr-tracker-bot
2023-07-26 6:17 Steve French
2023-07-26 18:42 ` pr-tracker-bot
2023-06-30 5:59 Steve French
2023-07-01 5:04 ` pr-tracker-bot
2023-06-20 4:45 Steve French
2023-06-20 19:01 ` pr-tracker-bot
2023-06-11 1:59 Steve French
2023-06-11 17:43 ` pr-tracker-bot
2023-05-21 5:14 Steve French
2023-05-21 18:06 ` Linus Torvalds
2023-05-21 18:32 ` Linus Torvalds
2023-05-21 19:03 ` Steve French
2023-05-21 19:21 ` Linus Torvalds
2023-05-22 4:38 ` Steve French
2023-05-22 8:04 ` ronnie sahlberg
2023-05-21 18:09 ` pr-tracker-bot
2023-05-06 0:19 Steve French
2023-05-06 2:20 ` pr-tracker-bot
2023-04-27 2:11 Steve French
2023-04-29 18:19 ` pr-tracker-bot
2023-04-07 4:16 Steve French
2023-04-07 20:56 ` pr-tracker-bot
2023-03-25 0:00 Steve French
2023-03-25 1:18 ` pr-tracker-bot
2023-02-22 4:15 Steve French
2023-02-22 22:26 ` pr-tracker-bot
2023-01-28 1:45 Steve French
2023-01-28 19:33 ` pr-tracker-bot
2023-01-10 3:13 Steve French
2023-01-10 11:36 ` pr-tracker-bot
2022-10-06 23:53 Steve French
2022-10-07 17:00 ` pr-tracker-bot
2022-08-19 5:03 Steve French
2022-08-19 21:14 ` pr-tracker-bot
2022-06-28 22:07 Steve French
2022-06-29 16:44 ` pr-tracker-bot
2022-06-01 6:20 Steve French
2022-06-01 19:34 ` pr-tracker-bot
2022-04-24 0:10 Steve French
2022-04-24 0:32 ` pr-tracker-bot
2022-04-01 18:40 Steve French
2022-04-01 21:41 ` Linus Torvalds
2022-04-01 21:45 ` pr-tracker-bot
2022-02-07 21:04 Steve French
2022-02-07 23:34 ` pr-tracker-bot
2021-11-27 21:43 Steve French
2021-11-27 22:52 ` pr-tracker-bot
2021-09-26 12:13 Steve French
2021-09-26 21:11 ` pr-tracker-bot
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='CAHk-=wikDs8v=Zk=Tdr7xRO3=9RWRa+2k068Upsk45uSx8r9nw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).