public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Ryan Zezeski <ryan@zinascii.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] 16614 cxgbe: support code for cxgbetool register read/write functionality
Date: Thu, 11 Jul 2024 05:40:36 -0600	[thread overview]
Message-ID: <m2plrkcg23.fsf@zinascii.com> (raw)
In-Reply-To: <17205924220.4ef75d.856794@composer.illumos.topicbox.com> (bharat via illumos-developer's message of "Wed, 10 Jul 2024 02:20:22 -0400")

"bharat via illumos-developer" <developer@lists.illumos.org> writes:

> Please review https://code.illumos.org/c/illumos-gate/+/3560
> These changes add register dump support to cxgbtool of cxgbe drivers.

Hi Bharat, thanks for the contribution.

I notice there are two CRs open against issue 16614. The first which you
linked in your original email, and this following one.

https://code.illumos.org/c/illumos-gate/+/3559/7

This later CR looks to add support for dumping the T6 regs, which I
believe you want to be part of the overall work for issue 16614. The
illumos project prefers to have logically related work as one commit;
that is, one commit per issue. I would roll these into one commit under
the 3560 CR. Furthermore, rather than removing the T4 regs I would also
add support for dumping T4 regs. Finally, the commit message should
match the issue title verbatim; so you'll want to change one or the
other so that they match.

Thanks,
Ryan

  reply	other threads:[~2024-07-11 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10  6:20 bharat
2024-07-11 11:40 ` Ryan Zezeski [this message]
2024-07-12 16:08   ` [developer] " bharat
2024-07-16 13:35   ` bharat

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=m2plrkcg23.fsf@zinascii.com \
    --to=ryan@zinascii.com \
    --cc=developer@lists.illumos.org \
    /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;
as well as URLs for NNTP newsgroup(s).