From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: mitake.hitoshi@lab.ntt.co.jp
Cc: stgt@vger.kernel.org, mitake.hitoshi@gmail.com
Subject: Re: [PATCH] tgtd: let event_need_refresh be a static variable
Date: Wed, 26 Feb 2014 15:03:52 +0900 [thread overview]
Message-ID: <20140226150118R.fujita.tomonori@lab.ntt.co.jp> (raw)
In-Reply-To: <1393392915-7682-1-git-send-email-mitake.hitoshi@lab.ntt.co.jp>
On Wed, 26 Feb 2014 14:35:15 +0900
Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp> wrote:
> The variable don't have to be visible from other source files.
>
> Signed-off-by: Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>
> ---
> usr/tgtd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks,
prev parent reply other threads:[~2014-02-26 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 5:35 [PATCH] tgtd: let event_need_refresh be a static variable Hitoshi Mitake
2014-02-26 6:03 ` FUJITA Tomonori [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=20140226150118R.fujita.tomonori@lab.ntt.co.jp \
--to=fujita.tomonori@lab.ntt.co.jp \
--cc=mitake.hitoshi@gmail.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=stgt@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).