From: Johannes Thumshirn <jthumshirn@suse.de>
To: yupeng <yupeng0921@gmail.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, keith.busch@intel.com,
axboe@fb.com, hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH v3 2/2] trace nvme submit queue status
Date: Mon, 17 Dec 2018 09:33:24 +0100 [thread overview]
Message-ID: <11554384-e0a9-0bde-97e9-228b29e6b641@suse.de> (raw)
In-Reply-To: <20181217080605.16867-2-yupeng0921@gmail.com>
Is the addition of a trace_pci.h really needed? Why can't you just put
it in trace.h?
Byte,
Johannes
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2018-12-17 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 8:06 [PATCH v3 1/2] share nvme trace event helper functions with other modules yupeng
2018-12-17 8:06 ` [PATCH v3 2/2] trace nvme submit queue status yupeng
2018-12-17 8:33 ` Johannes Thumshirn [this message]
2018-12-17 11:11 ` Christoph Hellwig
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=11554384-e0a9-0bde-97e9-228b29e6b641@suse.de \
--to=jthumshirn@suse.de \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yupeng0921@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
all inboxes | Powered by JetHome®