From: Helge Deller <deller@gmx.de>
To: Steve Grubb <sgrubb@redhat.com>, Laurent Bigonville <bigon@debian.org>
Cc: linux-audit@redhat.com, Ralf Treinen <treinen@debian.org>
Subject: Re: [PATCH] audit/userspace: add support for the parisc architecture
Date: Tue, 21 Jan 2014 22:00:15 +0100 [thread overview]
Message-ID: <52DEDFDF.1040703@gmx.de> (raw)
In-Reply-To: <20140121105922.6cddf7ca@ivy-bridge>
Hi Steve,
On 01/21/2014 04:59 PM, Steve Grubb wrote:
> Laurent Bigonville <bigon@debian.org> wrote:
>> Helge Deller <deller@gmx.de> a écrit :
>>> The patch below adds support for the parisc architecture to the
>>> audit userspace tool.
>>>
>>> It would be great if you could apply this patch to trunk.
>>>
>>> I posted the corresponding Linux kernel patch to the parisc mailing
>>> list (https://patchwork.kernel.org/patch/3046731/) and plan to push
>>> it upstream when the merge window for Linux kernel v3.13 opens.
>>>
>>> Signed-off-by: Helge Deller <deller@gmx.de>
>>
>> Any chances this patch could be merged? The debian package is now
>> including it (Ralf: I really would have preferred to see this merged
>> upstream _before_ it was pushed to the debian archive).
>
> Merging it means a commitment on my part to maintain it. I don't get
> much help at all on the user space side. So, one thing I consider is
> how many of these processors are in use. I have no idea about this one.
Not too many, we just started to make it work on debian again.
See the magenta line in this graph:
http://buildd.debian-ports.org/stats/
hppa is actually the CPU used in the HP-UX machines (before HP switched
HPUX to Itanium).
Is the work for the various architectures so much?
If you break one by mistake, either you will get patches which fixes it,
or otherwise you can just leave it broken unless somebody cares (and as long
it doesn't break you main architectures like x86-64, ppc64 and similiar of course).
Of course I will be helping for the hppa changes as long as I can, but I
don't expect too many changes/development coming, or?
> I can't say I have ever seen one in use anywhere. And I regret merging
> the alpha processor as it has very limited use and get no help
> maintaining it.
Please note, that I'm not subscribed to the audit-list yet.
I did sent an updated patch on January 18th to the one above, which I think
is still waiting for mailing-list moderator approval and didn't made it to
the mailing list yet...
Helge
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2014-01-21 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 17:56 [PATCH] audit/userspace: add support for the parisc architecture Helge Deller
2013-11-20 20:16 ` Helge Deller
2014-01-18 21:45 ` [PATCH] audit/userspace: add support for the parisc architecture (v2) Helge Deller
2014-01-21 9:34 ` [PATCH] audit/userspace: add support for the parisc architecture Laurent Bigonville
2014-01-21 12:11 ` Helge Deller
2014-01-21 15:59 ` Steve Grubb
2014-01-21 21:00 ` Helge Deller [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=52DEDFDF.1040703@gmx.de \
--to=deller@gmx.de \
--cc=bigon@debian.org \
--cc=linux-audit@redhat.com \
--cc=sgrubb@redhat.com \
--cc=treinen@debian.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).