All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
	Vincent Abriou <vincent.abriou@st.com>,
	David Airlie <airlied@linux.ie>,
	xie.baoyou@zte.com.cn, Arnd Bergmann <arnd@arndb.de>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/sti: mark symbols static where possible
Date: Thu, 8 Sep 2016 10:35:17 +0100	[thread overview]
Message-ID: <CACvgo51Ywjk7C-iNbsySaxWUQnC3zQBu90tPYqJfyg66SBs2kQ@mail.gmail.com> (raw)
In-Reply-To: <1473246307-889-1-git-send-email-baoyou.xie@linaro.org>

[Trimming down the CC list]

Hi Baoyou,

On 7 September 2016 at 12:05, Baoyou Xie <baoyou.xie@linaro.org> wrote:
> We get 2 warnings when building kernel with W=1:
As you're going through DRM I was wondering if you have a rough number
of warnings we get at the various W levels 1,2,...

Hope you'll have the time/interest to sort some of the W>1 ones as well :-)
Thanks
Emil

WARNING: multiple messages have this Message-ID (diff)
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	xie.baoyou@zte.com.cn,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	Vincent Abriou <vincent.abriou@st.com>
Subject: Re: [PATCH] drm/sti: mark symbols static where possible
Date: Thu, 8 Sep 2016 10:35:17 +0100	[thread overview]
Message-ID: <CACvgo51Ywjk7C-iNbsySaxWUQnC3zQBu90tPYqJfyg66SBs2kQ@mail.gmail.com> (raw)
In-Reply-To: <1473246307-889-1-git-send-email-baoyou.xie@linaro.org>

[Trimming down the CC list]

Hi Baoyou,

On 7 September 2016 at 12:05, Baoyou Xie <baoyou.xie@linaro.org> wrote:
> We get 2 warnings when building kernel with W=1:
As you're going through DRM I was wondering if you have a rough number
of warnings we get at the various W levels 1,2,...

Hope you'll have the time/interest to sort some of the W>1 ones as well :-)
Thanks
Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-09-08  9:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 11:05 [PATCH] drm/sti: mark symbols static where possible Baoyou Xie
2016-09-08  9:35 ` Emil Velikov [this message]
2016-09-08  9:35   ` Emil Velikov
2016-09-08  9:56   ` Arnd Bergmann
2016-09-08  9:56     ` Arnd Bergmann
2016-09-09 12:46     ` Emil Velikov
2016-09-08 10:07 ` Benjamin Gaignard
2016-09-15 11:39 Baoyou Xie
2016-09-15 15:15 ` Vincent ABRIOU
2016-09-15 15:15   ` Vincent ABRIOU
2016-09-25  7:57 Baoyou Xie
2016-09-27 16:35 ` Sean Paul
2016-09-27 16:35   ` Sean Paul
2016-09-27 19:07   ` Benjamin Gaignard
2016-09-27 19:07     ` Benjamin Gaignard
2016-09-28  7:27     ` Vincent ABRIOU
2016-09-28  7:27       ` Vincent ABRIOU
2016-09-29  9:27       ` Daniel Vetter
2016-09-29  9:27         ` Daniel Vetter

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=CACvgo51Ywjk7C-iNbsySaxWUQnC3zQBu90tPYqJfyg66SBs2kQ@mail.gmail.com \
    --to=emil.l.velikov@gmail.com \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=baoyou.xie@linaro.org \
    --cc=benjamin.gaignard@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vincent.abriou@st.com \
    --cc=xie.baoyou@zte.com.cn \
    /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.