From: Matthias Kaehlcke <mka@chromium.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Mark Charlebois <charlebm@gmail.com>,
Behan Webster <behanw@converseincode.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
Grant Grundler <grundler@chromium.org>,
Michael Davidson <md@google.com>,
Greg Hackmann <ghackmann@google.com>,
Peter Foley <pefoley2@pefoley.com>
Subject: Re: [PATCH] fs: compat: Remove warning from COMPATIBLE_IOCTL
Date: Thu, 20 Apr 2017 12:56:24 -0700 [thread overview]
Message-ID: <20170420195624.GJ128305@google.com> (raw)
In-Reply-To: <CAK8P3a13FJvMmK6VKYX=__Cp8GE87vpaORJyv3eBbdBS+L5OwQ@mail.gmail.com>
El Thu, Apr 20, 2017 at 10:45:47AM +0200 Arnd Bergmann ha dit:
> On Wed, Apr 19, 2017 at 11:37 PM, Matthias Kaehlcke <mka@chromium.org> wrote:
> > El Wed, Apr 19, 2017 at 10:48:47PM +0200 Arnd Bergmann ha dit:
> >> On Wed, Apr 19, 2017 at 8:14 PM, Matthias Kaehlcke <mka@chromium.org> wrote:
> >> > El Tue, Apr 04, 2017 at 11:07:20AM -0700 Matthias Kaehlcke ha dit:
>
> >> Aside from that, I see that you are upstreaming a number of clang
> >> related patches. I actually have a longer series of clang patches that
> >> I took from llvmlinux and hacked up to the point where I could
> >> build ARM randconfig kernels without any warnings or errors.
> >> If you are interested, I can separate the clang patches from my normal
> >> randconfig build tree and upload the git tree for you to look at and
> >> cherry-pick further patches.
> >
> > Sure, that would be interesting, though I won't promise to take up
> > everything :)
>
> I see now that almost all the patches I did have been picked up in the
> meantime, so I'm sure you already have most of the remaining contents
> as they come from the old llvmlinux project.
Yeah, I picked a subset of the llvmlinux patches from different
sources.
> For reference, I've uploaded my set to
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git
> next-20170420+llvmlinux
>
> This is rebased from the middle of a larger series, so there might be
> problems I introduce. Just have a look to see what you can use.
Thanks!
Matthias
prev parent reply other threads:[~2017-04-20 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 18:07 [PATCH] fs: compat: Remove warning from COMPATIBLE_IOCTL Matthias Kaehlcke
2017-04-19 18:14 ` Matthias Kaehlcke
2017-04-19 20:48 ` Arnd Bergmann
2017-04-19 21:37 ` Matthias Kaehlcke
2017-04-20 8:45 ` Arnd Bergmann
2017-04-20 19:56 ` Matthias Kaehlcke [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=20170420195624.GJ128305@google.com \
--to=mka@chromium.org \
--cc=arnd@arndb.de \
--cc=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=ghackmann@google.com \
--cc=grundler@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@google.com \
--cc=pefoley2@pefoley.com \
--cc=viro@zeniv.linux.org.uk \
/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).