linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rajashekar, Revanth" <revanth.rajashekar@intel.com>
To: Scott Bauer <sbauer@plzdonthack.me>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, axboe <axboe@kernel.dk>,
	jonathan.derrick@intel.com
Subject: Re: [PATCH 1/2] block: sed-opal: fix sparse warning: obsolete array init.
Date: Thu, 3 Oct 2019 09:57:44 -0600	[thread overview]
Message-ID: <1bef5039-174d-3700-6574-daf85225ffaa@intel.com> (raw)
In-Reply-To: <20191003154227.GB2450@hacktheplanet>


On 10/3/2019 9:42 AM, Scott Bauer wrote:
> On Wed, Oct 02, 2019 at 07:23:05PM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Fix sparse warning: (missing '=')
>> ../block/sed-opal.c:133:17: warning: obsolete array initializer, use C99 syntax
>>
>> Fixes: ff91064ea37c ("block: sed-opal: check size of shadow mbr")
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Jens Axboe <axboe@kernel.dk>
>> Cc: linux-block@vger.kernel.org
>> Cc: Jonas Rabenstein <jonas.rabenstein@studium.uni-erlangen.de>
>> Cc: David Kozub <zub@linux.fjfi.cvut.cz>
>> ---
> Un cc'd David and Jonas, +CC'd Jon and Revanth.
>
> This looks fine to me too.
>
> Reviewed-by: Scott Bauer <sbauer@plzdonthack.me>

Looks fine to me as well

Reviewed-by:  Revanth Rajashekar <revanth.rajashekar@intel.com>


  reply	other threads:[~2019-10-03 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03  2:23 [PATCH 1/2] block: sed-opal: fix sparse warning: obsolete array init Randy Dunlap
2019-10-03 15:42 ` Scott Bauer
2019-10-03 15:57   ` Rajashekar, Revanth [this message]
2019-10-03 16:01   ` Rajashekar, Revanth
2019-10-03 16:51 ` Derrick, Jonathan
2019-10-03 20:22 ` Jens Axboe

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=1bef5039-174d-3700-6574-daf85225ffaa@intel.com \
    --to=revanth.rajashekar@intel.com \
    --cc=axboe@kernel.dk \
    --cc=jonathan.derrick@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sbauer@plzdonthack.me \
    /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).