From: willy@linux.intel.com (Matthew Wilcox)
Subject: [PATCH] NVMe: Fix uninitialized iod compiler warning
Date: Fri, 27 Jul 2012 14:26:06 -0400 [thread overview]
Message-ID: <20120727182605.GN22985@linux.intel.com> (raw)
In-Reply-To: <1343411608-16133-1-git-send-email-keith.busch@intel.com>
On Fri, Jul 27, 2012@11:53:28AM -0600, Keith Busch wrote:
> - struct nvme_iod *iod;
> + struct nvme_iod *uninitialized_var(iod);
Thanks, applied.
next prev parent reply other threads:[~2012-07-27 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 17:53 [PATCH] NVMe: Fix uninitialized iod compiler warning Keith Busch
2012-07-27 18:26 ` Matthew Wilcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-25 22:04 [PATCH] NVMe: fix " Keith Busch
2012-07-26 14:50 ` Matthew Wilcox
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=20120727182605.GN22985@linux.intel.com \
--to=willy@linux.intel.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 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.