From: "Jan Beulich" <JBeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] mm: make opt_bootscrub non-init
Date: Mon, 26 Nov 2018 06:01:36 -0700 [thread overview]
Message-ID: <5BFBEEB002000078001FFF8B@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20181126124940.vjh7tm5ledpplkhq@mac>
>>> On 26.11.18 at 13:49, <roger.pau@citrix.com> wrote:
> On Mon, Nov 26, 2018 at 05:18:20AM -0700, Jan Beulich wrote:
>> Furthermore I doubt writing this down would help, because for
>> such apparently simple things no-one goes hunt for related
>> documentation. I think the only future proof course of action
>> would be to port Linux'es section mismatch handling and stop
>> allowing problematic cross references. That approach has
>> downsides though, which is why I'm not going to advocate it.
>
> Is Sparse the only option in this regard?
I'm specifically not talking about sparse, but about Linux'es
logic in scripts/mod/modpost.c.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-11-26 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 14:30 [PATCH] mm: make opt_bootscrub non-init Roger Pau Monne
2018-11-23 14:50 ` Andrew Cooper
2018-11-23 14:51 ` Julien Grall
2018-11-23 15:41 ` Sergey Dyasli
2018-11-24 11:46 ` Wei Liu
2018-11-26 10:06 ` Jan Beulich
2018-11-26 12:04 ` Roger Pau Monné
2018-11-26 12:18 ` Jan Beulich
2018-11-26 12:25 ` Julien Grall
2018-11-26 12:36 ` Jan Beulich
2018-11-26 12:49 ` Roger Pau Monné
2018-11-26 13:01 ` Jan Beulich [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=5BFBEEB002000078001FFF8B@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=sergey.dyasli@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.