mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Carlos Song <carlos.song@nxp.com>
Cc: Frank Li <frank.li@nxp.com>,
	"rongqianfeng@vivo.com" <rongqianfeng@vivo.com>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: spi-fsl-lpspi: fix watermark truncation caused by type cast
Date: Fri, 21 Nov 2025 14:23:17 +0000	[thread overview]
Message-ID: <7af6aa81-de6f-4ac7-b6dc-e4a79ae80afb@sirena.org.uk> (raw)
In-Reply-To: <VI2PR04MB11147DF123E2313B91CD8FBC7E8D5A@VI2PR04MB11147.eurprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

On Fri, Nov 21, 2025 at 08:18:17AM +0000, Carlos Song wrote:
> 
> Gently ping to avoid missing...

Please don't send content free pings and please allow a reasonable time
for review.  People get busy, go on holiday, attend conferences and so 
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review.  If there have been
review comments then people may be waiting for those to be addressed.

Sending content free pings adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-11-21 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17  3:03 carlos.song
2025-11-21  8:18 ` Carlos Song
2025-11-21 14:23   ` Mark Brown [this message]
2025-11-21  9:30 ` Daniel Baluta
2025-11-21 15:54 ` Frank Li
2025-11-21 16:19 ` Frank Li
2025-11-22 10:57   ` david laight
2025-11-25 15:11     ` Andy Shevchenko
2025-11-26  2:10       ` Carlos Song
2025-11-26  6:43         ` Andy Shevchenko
2025-11-26 10:02           ` Carlos Song
2025-11-21 16:24 ` Mark Brown
2025-11-22 10:48 ` david laight

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=7af6aa81-de6f-4ac7-b6dc-e4a79ae80afb@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=carlos.song@nxp.com \
    --cc=frank.li@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=rongqianfeng@vivo.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

all inboxes | Powered by JetHome®