From: Greg KH <gregkh@linuxfoundation.org>
To: fatihaltinpinar@gmail.com
Cc: matthias.bgg@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Staging: mt7621-dma: mtk-hsdma: fix a coding style issue
Date: Wed, 3 Jul 2019 18:32:32 +0200 [thread overview]
Message-ID: <20190703163232.GA29325@kroah.com> (raw)
In-Reply-To: <20190702080632.27470-1-fatihaltinpinar@gmail.com>
On Tue, Jul 02, 2019 at 11:06:32AM +0300, fatihaltinpinar@gmail.com wrote:
> From: Fatih ALTINPINAR <fatihaltinpinar@gmail.com>
>
> Fixed a coding style issue. Removed curly brackets of an one
> line if statement.
>
> Signed-off-by: Fatih ALTINPINAR <fatihaltinpinar@gmail.com>
> ---
> drivers/staging/mt7621-dma/mtk-hsdma.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/mt7621-dma/mtk-hsdma.c b/drivers/staging/mt7621-dma/mtk-hsdma.c
> index 0fbb9932d6bb..a58725dd2611 100644
> --- a/drivers/staging/mt7621-dma/mtk-hsdma.c
> +++ b/drivers/staging/mt7621-dma/mtk-hsdma.c
> @@ -664,9 +664,8 @@ static int mtk_hsdma_probe(struct platform_device *pdev)
> return -EINVAL;
>
> hsdma = devm_kzalloc(&pdev->dev, sizeof(*hsdma), GFP_KERNEL);
> - if (!hsdma) {
> + if (!hsdma)
> return -EINVAL;
> - }
>
> res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> base = devm_ioremap_resource(&pdev->dev, res);
This change is already in my tree, always be sure to work against the
proper kernel tree for doing new development.
thanks,
greg k-h
prev parent reply other threads:[~2019-07-03 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 8:06 [PATCH] Staging: mt7621-dma: mtk-hsdma: fix a coding style issue fatihaltinpinar
2019-07-03 16:32 ` Greg KH [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=20190703163232.GA29325@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=fatihaltinpinar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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