From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>,
"axboe@fb.com" <axboe@fb.com>
Subject: Re: [PATCH v2] nvme: find numa distance only if controller has valid numa id
Date: Tue, 16 Apr 2024 09:06:27 +0000 [thread overview]
Message-ID: <ccc7f60e-3c12-4245-afda-b4bdcb6c22ef@nvidia.com> (raw)
In-Reply-To: <391005cb-2a3d-426e-b539-30faf23c6efc@linux.ibm.com>
On 4/15/2024 11:53 PM, Nilay Shroff wrote:
> I don't know but checkpatch.pl didn't complain about my patch overshooting
> 80 chars width. Anyways, I will reformat the patch and resend.
>
> Thanks,
> --Nilay
checkpatch doesn't warn that anymore from what I remember, I've been
victim of relying on checkpatch then corrected on the list about 80
char.
-ck
prev parent reply other threads:[~2024-04-16 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 14:22 [PATCH v2] nvme: find numa distance only if controller has valid numa id Nilay Shroff
2024-04-16 2:36 ` Chaitanya Kulkarni
2024-04-16 6:53 ` Nilay Shroff
2024-04-16 9:06 ` Chaitanya Kulkarni [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=ccc7f60e-3c12-4245-afda-b4bdcb6c22ef@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@fb.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
/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