From: Jens Axboe <axboe@kernel.dk>
To: Tian Lan <tilan7663@gmail.com>
Cc: horms@kernel.org, linux-block@vger.kernel.org, lkp@intel.com,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
tian.lan@twosigma.com
Subject: Re: [PATCH 1/1] blk-mq: fix blk_mq_hw_ctx active request accounting
Date: Sat, 13 May 2023 19:39:54 -0600 [thread overview]
Message-ID: <a685e5d2-5da8-2ff2-c53d-dbf77fa9609d@kernel.dk> (raw)
In-Reply-To: <20230513221138.497270-1-tilan7663@gmail.com>
On 5/13/23 4:11 PM, Tian Lan wrote:
> Thanks Simon and Jens, I will remove the unused reference.
>
> And I'm sorry again, I'm very fresh in kernel development and still
> trying to learn the whole process. Hopefully this is the last time I will
> have to make the change (previously, I was compiling the entire kernel and
> missed the warning message). Thank you all for being patient with me and
> tolerate all the silly mistakes.
There should be zero warnings when compiling, so the easiest way to
check and catch it would be:
$ make -jX -s
as that will be quiet unless a warning or error is triggered.
--
Jens Axboe
next prev parent reply other threads:[~2023-05-14 1:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230513141234.8395-1-tilan7663@gmail.com>
2023-05-13 16:41 ` [PATCH 1/1] blk-mq: fix blk_mq_hw_ctx active request accounting kernel test robot
2023-05-13 19:05 ` Tian Lan
2023-05-13 20:54 ` Simon Horman
2023-05-13 21:15 ` Jens Axboe
2023-05-13 22:11 ` Tian Lan
2023-05-14 1:39 ` Jens Axboe [this message]
2023-05-15 12:28 ` Tian Lan
2023-05-13 22:12 ` Tian Lan
2023-05-14 1:52 ` Jens Axboe
2023-05-14 12:20 ` Ming Lei
2023-06-03 22:39 ` [PATCH] " Tian Lan
2023-06-04 0:47 ` Ming Lei
2023-06-03 22:39 ` [PATCH 1/1] " Tian Lan
2023-05-14 14:22 ` Ming Lei
2023-05-14 14:28 ` Tian Lan
2023-05-14 14:53 ` [PATCH] " Tian Lan
2023-05-15 5:54 ` Hannes Reinecke
2023-05-15 12:26 ` Tian Lan
2023-05-25 2:12 ` Ming Lei
2023-06-03 23:20 ` [PATCH 1/1] " Jens Axboe
2023-05-14 12:08 ` Ming Lei
2023-05-14 14:12 ` Tian Lan
2023-05-14 14:15 ` Ming Lei
2023-05-13 19:11 ` Tian Lan
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=a685e5d2-5da8-2ff2-c53d-dbf77fa9609d@kernel.dk \
--to=axboe@kernel.dk \
--cc=horms@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tian.lan@twosigma.com \
--cc=tilan7663@gmail.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