public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: martin.petersen@oracle.com,
	James.Bottomley@HansenPartnership.com,
	Kashyap Desai <kashyap.desai@avagotech.com>,
	Sumit Saxena <sumit.saxena@avagotech.com>,
	Uday Lingala <uday.lingala@avagotech.com>,
	"James E.J. Bottomley" <JBottomley@odin.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tomas Henzl <thenzl@redhat.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	megaraidlinux.pdl@avagotech.com
Subject: Re: [PATCH 3/3] megaraid_sas: add missing curly braces in ioctl handler
Date: Fri, 18 Mar 2016 15:23:50 -0400	[thread overview]
Message-ID: <yq14mc3a8u1.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1457965789-3373916-4-git-send-email-arnd@arndb.de> (Arnd Bergmann's message of "Mon, 14 Mar 2016 15:29:45 +0100")

>>>>> "Arnd" == Arnd Bergmann <arnd@arndb.de> writes:

Arnd> gcc-6 found a dubious indentation in the megasas_mgmt_fw_ioctl
Arnd> function:

Applied to 4.6/scsi-fixes.

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2016-03-18 19:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 14:29 gcc-6.0 warnings for scsi Arnd Bergmann
2016-03-14 14:29 ` [PATCH 1/3] aacraid: add missing curly braces Arnd Bergmann
2016-03-18 19:20   ` Martin K. Petersen
2016-03-18 20:50   ` Raghava Aditya Renukunta
2016-03-22  0:26   ` Martin K. Petersen
2016-03-14 14:29 ` [PATCH 2/3] lpfc: fix misleading indentation Arnd Bergmann
2016-03-14 15:19   ` Hannes Reinecke
2016-03-14 15:25     ` Arnd Bergmann
2016-03-14 15:26       ` Hannes Reinecke
2016-03-14 15:48         ` Ewan Milne
2016-03-14 22:27   ` Sebastian Herbszt
2016-03-18 19:22   ` Martin K. Petersen
2016-03-14 14:29 ` [PATCH 3/3] megaraid_sas: add missing curly braces in ioctl handler Arnd Bergmann
2016-03-14 15:20   ` Hannes Reinecke
2016-03-15 11:08   ` Sumit Saxena
2016-03-18 19:23   ` 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=yq14mc3a8u1.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=JBottomley@odin.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=kashyap.desai@avagotech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=megaraidlinux.pdl@avagotech.com \
    --cc=sumit.saxena@avagotech.com \
    --cc=thenzl@redhat.com \
    --cc=uday.lingala@avagotech.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