From: Sasha Levin <sashal@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: Stefan Metzmacher <metze@samba.org>, Tom Talpey <tom@talpey.com>,
linux-cifs@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 2/2] smb: client: let smbd_post_send_iter() respect the peers max_send_size and transmit all data
Date: Mon, 23 Jun 2025 15:48:35 -0400 [thread overview]
Message-ID: <aFmvk2YFA7zj40V6@lappy> (raw)
In-Reply-To: <CAH2r5mtqRX_pC+dCCFf44=m58vujkDJJLnZBGypycNfRSbj4DQ@mail.gmail.com>
On Mon, Jun 23, 2025 at 12:28:56PM -0500, Steve French wrote:
>Checkpatch will complain if you put a diff in the description so I
>suspect a link in the mainline patch description to the stable
>backported version of the patch is better than a diff in the
>description.
>
>Sasha,
>What is your preference for how to send a patch to mainline, that will
>not apply to stable, but a rebased version of patch is available for
>stable? Should the upstream patch have link to the stable rebased
>version? or just handle it as followup on the stable mailing list?
If you want us to not apply something, mark it with:
Cc: <stable+noautosel@kernel.org> # reason goes here, and must be present
And just send a backport to stable@
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-06-23 19:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 16:51 [PATCH 0/2] smb: client: fix problems with smbdirect/rdma mounts Stefan Metzmacher
2025-06-18 16:51 ` [PATCH 1/2] smb: client: fix max_sge overflow in smb_extract_folioq_to_rdma() Stefan Metzmacher
2025-06-19 11:41 ` David Howells
2025-06-19 19:07 ` Tom Talpey
2025-06-18 16:51 ` [PATCH 2/2] smb: client: let smbd_post_send_iter() respect the peers max_send_size and transmit all data Stefan Metzmacher
2025-06-19 11:49 ` David Howells
2025-06-19 19:22 ` Tom Talpey
2025-06-20 12:29 ` David Howells
2025-06-20 13:33 ` Tom Talpey
2025-06-20 14:56 ` David Howells
2025-06-25 7:59 ` David Howells
2025-06-23 15:46 ` Stefan Metzmacher
2025-06-23 17:28 ` Steve French
2025-06-23 19:48 ` Sasha Levin [this message]
2025-06-25 8:00 ` David Howells
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=aFmvk2YFA7zj40V6@lappy \
--to=sashal@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=metze@samba.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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