From: Ben Hutchings <ben@decadent.org.uk>
To: Jonathan Cameron <jic23@kernel.org>, Laura Abbott <labbott@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fixing tools using UAPI headers?
Date: Mon, 16 Jan 2017 02:06:41 +0000 [thread overview]
Message-ID: <1484532401.2998.27.camel@decadent.org.uk> (raw)
In-Reply-To: <7c8212f4-05e8-a9c6-b8c0-f516be48f9eb@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Sat, 2017-01-14 at 16:16 +0000, Jonathan Cameron wrote:
> On 14/01/17 00:24, Laura Abbott wrote:
> > Hi,
> >
> > I submitted https://marc.info/?l=linux-kernel&m=147343473231192&w=2
> > a while ago and it was suggested postponing any discussion until
> > after ksummit (https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2016-September/003829.html)
> > Did any discussion/hacking end up happening? There's interest in
> > building more of the tools in Fedora but I'm not excited about
> > doing this if more of the tools are prone to header problems.
> >
> > Thanks,
> > Laura
> >
>
> Hi Laura,
>
> I'm afraid I wasn't at the kernel summit, but I haven't had any feedback
> on this being discussed, so you are wise to bring it up again.
>
> Ben, did it come up to your knowledge?
Certainly not on the core day, and if it happened some other day then I
missed it.
Ben.
> If not, I guess we fall back to good old reliable email to discuss it
> now.
>
> Jonathan
--
Ben Hutchings
Every program is either trivial or else contains at least one bug
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-01-16 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 0:24 Laura Abbott
2017-01-14 16:16 ` Jonathan Cameron
2017-01-16 2:06 ` Ben Hutchings [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=1484532401.2998.27.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=jic23@kernel.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome