From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v3 1/4] drm/i915/tc: rename mtl_tc_port_get_pin_assignment_mask()
Date: Wed, 16 Aug 2023 09:08:44 +0000 [thread overview]
Message-ID: <dd9c0014d0a019a326da29705adf548da32f4e32.camel@intel.com> (raw)
In-Reply-To: <SN7PR11MB67503D9744E5F01AFB48DB86E315A@SN7PR11MB6750.namprd11.prod.outlook.com>
On Wed, 2023-08-16 at 08:13 +0000, Kandpal, Suraj wrote:
> > This function doesn't really return the pin assignment mask, but
> > the max lane
> > count derived from that. So rename the function to
> > mtl_tc_port_get_max_lane_count() to better reflect what it really
> > does.
> >
> Maybe also add the version changes on commit messages here as cover
> letter ends up getting discarded
Ah, right. I discussed this with someone else before and we agreed to
disagree. 🙂 I don't really see the point in having the change history
in the commit itself for the mainline. The discussions should be
openly available in the mailing list archives, so duplicating it in the
commit logs, IMHO, is moot.
A link in the commit log to lore, for instance, would add much more
value IMHO.
But anyway, since this guideline was already in place when I came, I
will (almost grudgingly) comply. 😉
>
> With that fixed
>
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
Thanks!
--
Cheers,
Luca.
next prev parent reply other threads:[~2023-08-16 9:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 11:11 [Intel-gfx] [PATCH v3 0/4] drm/i915/tc: some clean-ups in max lane count handling code Luca Coelho
2023-07-21 11:11 ` [Intel-gfx] [PATCH v3 1/4] drm/i915/tc: rename mtl_tc_port_get_pin_assignment_mask() Luca Coelho
2023-08-16 8:13 ` Kandpal, Suraj
2023-08-16 9:08 ` Coelho, Luciano [this message]
2023-08-19 3:50 ` Lucas De Marchi
2023-08-24 7:48 ` Coelho, Luciano
2023-07-21 11:11 ` [Intel-gfx] [PATCH v3 2/4] drm/i915/tc: make intel_tc_port_get_lane_mask() static Luca Coelho
2023-08-16 8:44 ` Kandpal, Suraj
2023-07-21 11:11 ` [Intel-gfx] [PATCH v3 3/4] drm/i915/tc: move legacy code out of the main _max_lane_count() func Luca Coelho
2023-08-16 8:54 ` Kandpal, Suraj
2023-08-24 11:06 ` Coelho, Luciano
2023-08-24 11:10 ` Kandpal, Suraj
2023-08-24 11:12 ` Kandpal, Suraj
2023-08-24 11:14 ` Coelho, Luciano
2023-07-21 11:11 ` [Intel-gfx] [PATCH v3 4/4] drm/i915/tc: remove "fia" from intel_tc_port_fia_max_lane_count() Luca Coelho
2023-08-19 3:53 ` Lucas De Marchi
2023-08-24 5:45 ` Kandpal, Suraj
2023-07-21 12:22 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/tc: some clean-ups in max lane count handling code (rev3) Patchwork
2023-08-19 3:47 ` [Intel-gfx] [PATCH v3 0/4] drm/i915/tc: some clean-ups in max lane count handling code Lucas De Marchi
2023-08-21 17:27 ` Kandpal, Suraj
2023-08-24 7:51 ` Coelho, Luciano
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=dd9c0014d0a019a326da29705adf548da32f4e32.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=suraj.kandpal@intel.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