From: Simon Ser <contact@emersion.fr>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev,
dri-devel@lists.freedesktop.org,
Pekka Paalanen <pekka.paalanen@collabora.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/connector: Add newline to debug printk
Date: Fri, 25 Aug 2023 23:32:42 +0000 [thread overview]
Message-ID: <sqyPw9vZ5TuRr6bQT59K00AB1wM5QdkEdK-qUEWeesjx_nin5LzSAL1NSIOIV5PD0pKqpzqscQs0FRAjMmD98L3WcNMt4-l7J0mxqIMr7zQ=@emersion.fr> (raw)
In-Reply-To: <20230825233118.2689222-1-swboyd@chromium.org>
Reviewed-by: Simon Ser <contact@emersion.fr>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Ser <contact@emersion.fr>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Pekka Paalanen <pekka.paalanen@collabora.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
patches@lists.linux.dev, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/connector: Add newline to debug printk
Date: Fri, 25 Aug 2023 23:32:42 +0000 [thread overview]
Message-ID: <sqyPw9vZ5TuRr6bQT59K00AB1wM5QdkEdK-qUEWeesjx_nin5LzSAL1NSIOIV5PD0pKqpzqscQs0FRAjMmD98L3WcNMt4-l7J0mxqIMr7zQ=@emersion.fr> (raw)
In-Reply-To: <20230825233118.2689222-1-swboyd@chromium.org>
Reviewed-by: Simon Ser <contact@emersion.fr>
next prev parent reply other threads:[~2023-08-25 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 23:31 [PATCH] drm/connector: Add newline to debug printk Stephen Boyd
2023-08-25 23:31 ` Stephen Boyd
2023-08-25 23:32 ` Simon Ser [this message]
2023-08-25 23:32 ` Simon Ser
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='sqyPw9vZ5TuRr6bQT59K00AB1wM5QdkEdK-qUEWeesjx_nin5LzSAL1NSIOIV5PD0pKqpzqscQs0FRAjMmD98L3WcNMt4-l7J0mxqIMr7zQ=@emersion.fr' \
--to=contact@emersion.fr \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=patches@lists.linux.dev \
--cc=pekka.paalanen@collabora.com \
--cc=swboyd@chromium.org \
--cc=tzimmermann@suse.de \
/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.