Re: [GIT PULL] smb client fixes for 7.3-rc1

[Paulo Alcantara <pc@manguebit.org>]

Linus Torvalds <torvalds@linux-foundation.org> writes:

> On Mon, 24 Aug 2026 at 15:06, Paulo Alcantara <pc@manguebit.org> wrote:
>>
>> Attached is a pull request for the patches if you
>> are willing to take them immediately.
>
> I think I might as well take them immediately and treat it as a merge
> window update pull, even if it looks like only one of these commits
> have been in linux-next. Not the comon situation, after all.

ACK.  Thanks.

> I assume there is nothing else pending right now?

Nope.

> Also, I've mentioned this elsewhere, but since I'm starting to see
> more pulls from you I'll mention it explicitly here too: the merge
> message should describe what the changes do, not irrelevant
> technicalities.
>
> And one such irrelevant technicality is how many patches there are.
> Nobody cares.
>
> Would it have been any different if it had been done as one single
> larger patch? No.
>
> And if people do care about the "five patches" part, they would be
> looking at the individual commits, not reading the merge commit
> message.

ACK.  Sorry for attempting to follow the wrong pattern then.

> So I mention this because I reacted to "five sensitive data leak fixes".
>
> The "five" is uninteresting, and the "data leak fixes" aren't.
>
> Those commits are clearing keys after use. That's not fixing a leak,
> that's just hardening in case a leak exists elsewere.
>
> So I rewrote it as "clear sensitive data after use".

Makes sense, thanks.

> This is not a problem, but I'll be happier if I don't feel like I need
> to edit things more than necessary, so I'm mentioning this in the hope
> that people will stop that pattern of numbering patches in particular.

ACK.