From: Borislav Petkov <bp@alien8.de>
To: Colin King <colin.king@canonical.com>, Tony Luck <tony.luck@intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Doug Thompson <dougthompson@xmission.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC: sb_edac: remove null pointer check on array pci_tad
Date: Fri, 9 Sep 2016 14:50:24 +0200 [thread overview]
Message-ID: <20160909125024.5ozjo2swdddd63ra@pd.tnic> (raw)
In-Reply-To: <20160908083801.14766-1-colin.king@canonical.com>
+ Tony.
On Thu, Sep 08, 2016 at 09:38:01AM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> pvt->pci_tad is a NUM_CHANNELS array of struct pci_dev pointers and
> hence cannot be null, so the pull pointer check on pci_tad is
> redundant. Remove it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/edac/sb_edac.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/edac/sb_edac.c b/drivers/edac/sb_edac.c
> index ce0067b..5477522 100644
> --- a/drivers/edac/sb_edac.c
> +++ b/drivers/edac/sb_edac.c
> @@ -2474,7 +2474,7 @@ static int sbridge_mci_bind_devs(struct mem_ctl_info *mci,
>
> /* Check if everything were registered */
> if (!pvt->pci_sad0 || !pvt->pci_sad1 || !pvt->pci_ha0 ||
> - !pvt-> pci_tad || !pvt->pci_ras || !pvt->pci_ta)
> + !pvt->pci_ras || !pvt->pci_ta)
> goto enodev;
>
> if (saw_chan_mask != 0x0f)
> @@ -2563,8 +2563,7 @@ static int ibridge_mci_bind_devs(struct mem_ctl_info *mci,
>
> /* Check if everything were registered */
> if (!pvt->pci_sad0 || !pvt->pci_ha0 || !pvt->pci_br0 ||
> - !pvt->pci_br1 || !pvt->pci_tad || !pvt->pci_ras ||
> - !pvt->pci_ta)
> + !pvt->pci_br1 || !pvt->pci_ras || !pvt->pci_ta)
> goto enodev;
>
> if (saw_chan_mask != 0x0f && /* -EN */
> --
> 2.9.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-edac" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-09-09 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 8:38 Colin King
2016-09-09 12:50 ` Borislav Petkov [this message]
2016-09-12 18:32 ` Borislav Petkov
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=20160909125024.5ozjo2swdddd63ra@pd.tnic \
--to=bp@alien8.de \
--cc=colin.king@canonical.com \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--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
all inboxes | Powered by JetHome®