From: Dan Carpenter <dan.carpenter@linaro.org>
To: John Meneghini <jmeneghi@redhat.com>
Cc: Karan Tilak Kumar <kartilak@cisco.com>,
sebaddel@cisco.com, arulponn@cisco.com, djhawar@cisco.com,
gcboffa@cisco.com, mkai2@cisco.com, satishkh@cisco.com,
aeasi@cisco.com, jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v7 07/15] scsi: fnic: Add and integrate support for FDMI
Date: Tue, 14 Jan 2025 12:59:33 +0300 [thread overview]
Message-ID: <b3c29afc-c49b-42af-9733-7cf2b934cd90@stanley.mountain> (raw)
In-Reply-To: <d18ed046-0d16-49d6-b666-8ef8ee20f6d2@redhat.com>
On Mon, Jan 13, 2025 at 12:35:03PM -0500, John Meneghini wrote:
> Just a note to say that these patches are important to Red Hat and we
> are actively engaged in back porting and testing these patches in to
> RHEL-9 and RHEL-10.
>
> I think these issues that Dan has pointed out are all issues which
> can be addressed in a follow up patch.
I mean we already merged this. I only got involved because of static
checker issues in linux-next.
What I'm complaining about is not so much any specific issue but just
that the process was not followed. Normally this patch would not
be merged. If anyone sent a patch like this to drivers/staging it
would have triggered Greg's patch-bot automated response:
- Your patch did many different things all at once, making it difficult
to review. All Linux kernel patches need to only do one thing at a
time. If you need to do multiple things (such as clean up all coding
style issues in a file/driver), do it in a sequence of patches, each
one doing only one thing. This will make it easier to review the
patches to ensure that they are correct, and to help alleviate any
merge issues that larger patches can cause.
This rule is the same in every subsystem. No one wants to merge a patch
like this. But what happened is the patch sat on the list and only
Hannes and Martin were doing any review. Karan was left doing all the
work with no help or guidance. Eventually Martin has to give up right?
The patchset isn't up to normal standards but it's basically okay and
Martin can't do every single thing by himself and eventually it's pretty
clear no one else is coming to help. It is what it is etc.
Please understand this in the gentlest way. Next time if something is
important then assign an engineer to help out. It would have taken a day
to prepare this patchset for merging. You had seven months. It's not
fair to show up five days before the merge window asking for special
exemptions from the review process. Maintainers and reviewers are
already overworked, they shouldn't have to work around your deadlines.
From what I've seen Karan is absolutely doing a good job addressing the
problems I reported so it's fine. But normally this is not how it works.
regards,
dan carpenter
next prev parent reply other threads:[~2025-01-14 9:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 2:02 [PATCH v7 00/15] Introduce support for Fabric Discovery and Karan Tilak Kumar
2024-12-12 2:02 ` [PATCH v7 01/15] scsi: fnic: Replace shost_printk with dev_info/dev_err Karan Tilak Kumar
2024-12-12 2:02 ` [PATCH v7 02/15] scsi: fnic: Add headers and definitions for FDLS Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 03/15] scsi: fnic: Add support for fabric based solicited requests and responses Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 04/15] scsi: fnic: Add support for target " Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 05/15] scsi: fnic: Add support for unsolicited " Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 06/15] scsi: fnic: Add Cisco hardware model names Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 07/15] scsi: fnic: Add and integrate support for FDMI Karan Tilak Kumar
2025-01-07 12:30 ` Dan Carpenter
2025-01-08 21:47 ` Karan Tilak Kumar (kartilak)
2025-01-13 17:35 ` John Meneghini
2025-01-13 20:28 ` Karan Tilak Kumar (kartilak)
2025-01-14 9:59 ` Dan Carpenter [this message]
2025-01-14 15:15 ` John Meneghini
2025-01-15 1:03 ` Karan Tilak Kumar (kartilak)
2025-01-16 6:29 ` Dan Carpenter
2024-12-12 2:03 ` [PATCH v7 08/15] scsi: fnic: Add and integrate support for FIP Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 09/15] scsi: fnic: Add functionality in fnic to support FDLS Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 10/15] scsi: fnic: Modify IO path to use FDLS Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 11/15] scsi: fnic: Modify fnic interfaces " Karan Tilak Kumar
2025-01-07 13:18 ` Dan Carpenter
2025-01-08 21:40 ` Karan Tilak Kumar (kartilak)
2025-01-09 8:23 ` Dan Carpenter
2025-01-10 9:37 ` Karan Tilak Kumar (kartilak)
2024-12-12 2:03 ` [PATCH v7 12/15] scsi: fnic: Add stats and related functionality Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 13/15] scsi: fnic: Code cleanup Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 14/15] scsi: fnic: Add support to handle port channel RSCN Karan Tilak Kumar
2024-12-12 2:03 ` [PATCH v7 15/15] scsi: fnic: Increment driver version Karan Tilak Kumar
2025-01-02 21:09 ` [PATCH v7 00/15] Introduce support for Fabric Discovery and Martin K. Petersen
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=b3c29afc-c49b-42af-9733-7cf2b934cd90@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=aeasi@cisco.com \
--cc=arulponn@cisco.com \
--cc=djhawar@cisco.com \
--cc=gcboffa@cisco.com \
--cc=jejb@linux.ibm.com \
--cc=jmeneghi@redhat.com \
--cc=kartilak@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=mkai2@cisco.com \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.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®