linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libata: Remove FIXME comment in atapi_eh_request_sense
Date: Wed, 7 Jan 2015 10:08:09 -0500	[thread overview]
Message-ID: <20150107150809.GA4395@htj.dyndns.org> (raw)
In-Reply-To: <1420609492-19422-1-git-send-email-xerofoify@gmail.com>

On Wed, Jan 07, 2015 at 12:44:52AM -0500, Nicholas Krause wrote:
> Remove the FIXME comment in  atapi_eh_request_sense () asking whether
> memset of sense buffer is necessary.  The buffer may be partially or
> fully filled by the device.  We want it to be cleared.
> 
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>

Applied to libata/for-3.20.  Thanks.

-- 
tejun

           reply	other threads:[~2015-01-07 15:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1420609492-19422-1-git-send-email-xerofoify@gmail.com>]

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=20150107150809.GA4395@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xerofoify@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;
as well as URLs for NNTP newsgroup(s).