From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Fabian Frederick <fabf@skynet.be>,
Anil Gurumurthy <anil.gurumurthy@qlogic.com>,
Christoph Hellwig <hch@lst.de>,
Guenter Roeck <linux@roeck-us.net>,
Ben Hutchings <ben@decadent.org.uk>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH RESEND] bfa: deinline __bfa_trc() and __bfa_trc32()
Date: Thu, 11 Feb 2016 09:41:32 -0500 [thread overview]
Message-ID: <yq1io1v5mxv.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1454618448-1381-1-git-send-email-dvlasenk@redhat.com> (Denys Vlasenko's message of "Thu, 4 Feb 2016 21:40:48 +0100")
>>>>> "Denys" == Denys Vlasenko <dvlasenk@redhat.com> writes:
Denys> __bfa_trc() compiles to 115 bytes of machine code. With this
Denys> .config: http://busybox.net/~vda/kernel_config there are 1494
Denys> calls of __bfa_trc().
Applied to 4.6/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2016-02-11 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 20:40 [PATCH RESEND] bfa: deinline __bfa_trc() and __bfa_trc32() Denys Vlasenko
2016-02-10 17:28 ` Martin K. Petersen
2016-02-11 8:42 ` Anil Gurumurthy
2016-02-11 14:41 ` Martin K. Petersen [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=yq1io1v5mxv.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=anil.gurumurthy@qlogic.com \
--cc=ben@decadent.org.uk \
--cc=dvlasenk@redhat.com \
--cc=fabf@skynet.be \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.