From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Colin King <colin.king@canonical.com>
Cc: Adaptec OEM Raid Solutions <aacraid@microsemi.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: dpt_i2o: clean up indentation issues, remove spaces
Date: Tue, 19 Mar 2019 21:11:02 +0000 [thread overview]
Message-ID: <yq11s32d0yh.fsf@oracle.com> (raw)
In-Reply-To: <20190123125319.17193-1-colin.king@canonical.com> (Colin King's message of "Wed, 23 Jan 2019 12:53:19 +0000")
Colin,
> There are several lines where the indentation has an extra space, fix
> this by removing the spaces.
Applied to 5.2/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Colin King <colin.king@canonical.com>
Cc: Adaptec OEM Raid Solutions <aacraid@microsemi.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: dpt_i2o: clean up indentation issues, remove spaces
Date: Tue, 19 Mar 2019 17:11:02 -0400 [thread overview]
Message-ID: <yq11s32d0yh.fsf@oracle.com> (raw)
In-Reply-To: <20190123125319.17193-1-colin.king@canonical.com> (Colin King's message of "Wed, 23 Jan 2019 12:53:19 +0000")
Colin,
> There are several lines where the indentation has an extra space, fix
> this by removing the spaces.
Applied to 5.2/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-03-19 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 12:53 [PATCH] scsi: dpt_i2o: clean up indentation issues, remove spaces Colin King
2019-03-19 21:11 ` Martin K. Petersen [this message]
2019-03-19 21:11 ` Martin K. Petersen
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=yq11s32d0yh.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=aacraid@microsemi.com \
--cc=colin.king@canonical.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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.