From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: mvsas: Don't emit __LINE__ in debug messages
Date: Thu, 14 May 2026 22:05:58 -0400 [thread overview]
Message-ID: <yq1jyt55sw2.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260427174545.2014499-2-u.kleine-koenig@baylibre.com> ("Uwe Kleine-König (The Capable Hub)"'s message of "Mon, 27 Apr 2026 19:45:46 +0200")
Uwe,
> __LINE__ changes quite easily for cleanup commits. So when checking if a
> cleanup patch introduces changes to the resulting binary each usage of
> __LINE__ is source of annoyance.
Applied to 7.2/scsi-staging, thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2026-05-15 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:45 [PATCH] scsi: mvsas: Don't emit __LINE__ in debug messages Uwe Kleine-König (The Capable Hub)
2026-05-15 2:05 ` Martin K. Petersen [this message]
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=yq1jyt55sw2.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=u.kleine-koenig@baylibre.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