From: Leon Romanovsky <leonro@mellanox.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Andrey Konovalov <adech.fo@gmail.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Ingo Molnar <mingo@kernel.org>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Michal Marek <mmarek@suse.cz>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH rdma-next 0/2] Fix kasan compilation warnings
Date: Tue, 12 May 2020 13:09:36 +0300 [thread overview]
Message-ID: <20200512100936.GJ4814@unreal> (raw)
In-Reply-To: <20200512063728.17785-1-leon@kernel.org>
On Tue, May 12, 2020 at 09:37:26AM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> Hi,
>
> The following two fixes are adding missing function prototypes
> declarations to internal kasan header in order to eliminate compilation
> warnings.
>
> Thanks
Sorry for forgetting to clean subject, the patches are not "rdma-next"
but MM related.
Thanks
>
> Leon Romanovsky (2):
> kasan: fix compilation warnings due to missing function prototypes
> kasan: add missing prototypes to fix compilation warnings
>
> mm/kasan/common.c | 3 ---
> mm/kasan/kasan.h | 15 +++++++++++++++
> 2 files changed, 15 insertions(+), 3 deletions(-)
>
> --
> 2.26.2
>
>
next prev parent reply other threads:[~2020-05-12 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 6:37 [PATCH rdma-next 0/2] Fix kasan compilation warnings Leon Romanovsky
2020-05-12 6:37 ` [PATCH rdma-next 1/2] kasan: fix compilation warnings due to missing function prototypes Leon Romanovsky
2020-05-12 6:37 ` [PATCH rdma-next 2/2] kasan: add missing prototypes to fix compilation warnings Leon Romanovsky
2020-05-12 10:09 ` Leon Romanovsky [this message]
2020-05-12 15:34 ` [PATCH rdma-next 0/2] Fix kasan " Andrey Konovalov
2020-05-12 16:11 ` Leon Romanovsky
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=20200512100936.GJ4814@unreal \
--to=leonro@mellanox.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=peterz@infradead.org \
/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).