Linux EDAC development
 help / color / mirror / Atom feed
From: David Thompson <davthompson@nvidia.com>
To: <bp@alien8.de>, <tony.luck@intel.com>, <james.morse@arm.com>,
	<mchehab@kernel.org>, <rric@kernel.org>
Cc: <shravankr@nvidia.com>, <linux-edac@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	David Thompson <davthompson@nvidia.com>
Subject: [PATCH v1 1/2] EDAC/bluefield: fix white space in bluefield_edac_mc_probe
Date: Wed, 12 Jun 2024 15:38:30 -0400	[thread overview]
Message-ID: <20240612193831.25913-2-davthompson@nvidia.com> (raw)
In-Reply-To: <20240612193831.25913-1-davthompson@nvidia.com>

This patch removes an empty line in bluefield_edac_mc_probe().

Signed-off-by: David Thompson <davthompson@nvidia.com>
Reviewed-by: Shravan Kumar Ramani <shravankr@nvidia.com>
---
 drivers/edac/bluefield_edac.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/edac/bluefield_edac.c b/drivers/edac/bluefield_edac.c
index 5b3164560648..1f6f39a7dbf3 100644
--- a/drivers/edac/bluefield_edac.c
+++ b/drivers/edac/bluefield_edac.c
@@ -320,7 +320,6 @@ static int bluefield_edac_mc_probe(struct platform_device *pdev)
 	edac_mc_free(mci);
 
 	return ret;
-
 }
 
 static void bluefield_edac_mc_remove(struct platform_device *pdev)
-- 
2.30.1


  reply	other threads:[~2024-06-12 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 19:38 [PATCH v1 0/2] Style fixes for EDAC/bluefield driver David Thompson
2024-06-12 19:38 ` David Thompson [this message]
2024-06-12 20:00   ` [PATCH v1 1/2] EDAC/bluefield: fix white space in bluefield_edac_mc_probe Borislav Petkov
2024-06-13 15:06     ` David Thompson
2024-06-13 15:11       ` Borislav Petkov
2024-06-12 19:38 ` [PATCH v1 2/2] EDAC/bluefield: fix prefix for GET_DIMM_INFO defines David Thompson

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=20240612193831.25913-2-davthompson@nvidia.com \
    --to=davthompson@nvidia.com \
    --cc=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rric@kernel.org \
    --cc=shravankr@nvidia.com \
    --cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox