From: david.vrabel@citrix.com (David Vrabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [PATCH v2 0/5] xen: avoid module usage in non-modular code
Date: Mon, 21 Mar 2016 15:17:00 +0000 [thread overview]
Message-ID: <56F0106C.3030200@citrix.com> (raw)
In-Reply-To: <20160320002321.GX23251@windriver.com>
On 20/03/16 00:23, Paul Gortmaker wrote:
> [[PATCH v2 0/5] xen: avoid module usage in non-modular code] On 21/02/2016 (Sun 19:06) Paul Gortmaker wrote:
>
>> This series of commits is a part of a larger project to ensure
>> people don't reference modular support functions in non-modular
>> code. Overall there was roughly 5k lines of dead code in the
>> kernel due to this. So far we've fixed several areas, like tty,
>> x86, net, ... and we continue to work on other areas.
>
> Just wondering if this is still pending for this merge window; Stefano
> had reviewed the two commits he wanted changed vs. v1 and this v2 was
> sent approximately a month ago w/o any further change requests.
Sorry. While I was checking for pending series for 4.6 I accidentally
looked at v1 and saw outstanding comments and skipped it.
I've now applied this series, thanks.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
<linux-kernel@vger.kernel.org>
Cc: Russell King <linux@arm.linux.org.uk>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
<xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Xen-devel] [PATCH v2 0/5] xen: avoid module usage in non-modular code
Date: Mon, 21 Mar 2016 15:17:00 +0000 [thread overview]
Message-ID: <56F0106C.3030200@citrix.com> (raw)
In-Reply-To: <20160320002321.GX23251@windriver.com>
On 20/03/16 00:23, Paul Gortmaker wrote:
> [[PATCH v2 0/5] xen: avoid module usage in non-modular code] On 21/02/2016 (Sun 19:06) Paul Gortmaker wrote:
>
>> This series of commits is a part of a larger project to ensure
>> people don't reference modular support functions in non-modular
>> code. Overall there was roughly 5k lines of dead code in the
>> kernel due to this. So far we've fixed several areas, like tty,
>> x86, net, ... and we continue to work on other areas.
>
> Just wondering if this is still pending for this merge window; Stefano
> had reviewed the two commits he wanted changed vs. v1 and this v2 was
> sent approximately a month ago w/o any further change requests.
Sorry. While I was checking for pending series for 4.6 I accidentally
looked at v1 and saw outstanding comments and skipped it.
I've now applied this series, thanks.
David
next prev parent reply other threads:[~2016-03-21 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 0:06 [PATCH v2 0/5] xen: avoid module usage in non-modular code Paul Gortmaker
2016-02-22 0:06 ` Paul Gortmaker
2016-02-22 0:06 ` [PATCH v2 1/5] xen: audit usages of module.h ; remove unnecessary instances Paul Gortmaker
2016-02-22 0:06 ` Paul Gortmaker
2016-02-22 0:06 ` Paul Gortmaker
2016-02-22 0:06 ` [PATCH v2 2/5] drivers/xen: make [xen-]ballon explicitly non-modular Paul Gortmaker
2016-02-22 0:06 ` Paul Gortmaker
2016-02-22 0:06 ` [PATCH v2 3/5] drivers/xen: make xenbus_dev_[front/back]end " Paul Gortmaker
2016-02-22 0:06 ` Paul Gortmaker
2016-02-22 0:06 ` [PATCH v2 4/5] drivers/xen: make sys-hypervisor.c " Paul Gortmaker
2016-02-22 11:25 ` Stefano Stabellini
2016-02-22 11:25 ` Stefano Stabellini
2016-02-22 0:06 ` Paul Gortmaker
2016-02-22 0:06 ` [PATCH v2 5/5] drivers/xen: make platform-pci.c " Paul Gortmaker
2016-02-22 0:06 ` Paul Gortmaker
2016-02-22 11:27 ` Stefano Stabellini
2016-02-22 11:27 ` Stefano Stabellini
2016-03-20 0:23 ` [PATCH v2 0/5] xen: avoid module usage in non-modular code Paul Gortmaker
2016-03-20 0:23 ` Paul Gortmaker
2016-03-20 0:23 ` Paul Gortmaker
2016-03-21 15:17 ` David Vrabel
2016-03-21 15:17 ` David Vrabel [this message]
2016-03-21 15:17 ` [Xen-devel] " David Vrabel
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=56F0106C.3030200@citrix.com \
--to=david.vrabel@citrix.com \
--cc=linux-arm-kernel@lists.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 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.