From: Andrzej Hajda <a.hajda@samsung.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
linux-kernel@vger.kernel.org
Cc: kernel@collabora.com, Daniel Vetter <daniel.vetter@ffwll.ch>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Archit Taneja <architt@codeaurora.org>,
zain wang <wzz@rock-chips.com>,
dri-devel@lists.freedesktop.org, Lin Huang <hl@rock-chips.com>,
David Airlie <airlied@linux.ie>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Sean Paul <seanpaul@chromium.org>,
Jeffy Chen <jeffy.chen@rock-chips.com>
Subject: Re: [PATCH v2] drm/bridge: analogix_dp: Fix misleading indentation reported by smatch
Date: Mon, 29 Oct 2018 14:52:52 +0100 [thread overview]
Message-ID: <f2bb09b8-c916-dd2a-03a6-f2bec157c117@samsung.com> (raw)
In-Reply-To: <20181016095336.15656-1-enric.balletbo@collabora.com>
On 16.10.2018 11:53, Enric Balletbo i Serra wrote:
> This patch avoids that building the bridge/analogix source code with
> smatch triggers complaints about inconsistent indenting. It also fixes
> a typo in DRM_ERROR message, attch is replaced for attach.
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Queued to drm-misc-next.
Regards
Andrzej
prev parent reply other threads:[~2018-10-29 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181016095350epcas4p3a71b29adb3fbeb8075568de20d43e3a0@epcas4p3.samsung.com>
2018-10-16 9:53 ` [PATCH v2] drm/bridge: analogix_dp: Fix misleading indentation reported by smatch Enric Balletbo i Serra
2018-10-29 13:52 ` Andrzej Hajda [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=f2bb09b8-c916-dd2a-03a6-f2bec157c117@samsung.com \
--to=a.hajda@samsung.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=enric.balletbo@collabora.com \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=seanpaul@chromium.org \
--cc=wzz@rock-chips.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;
as well as URLs for NNTP newsgroup(s).