LKML Archive on
 help / color / Atom feed
From: Greg Kroah-Hartman <>
To: Georgi Djakov <>
Cc: Linux PM list <>,
	"" <>
Subject: Re: [GIT PULL] interconnect changes for 5.5
Date: Thu, 7 Nov 2019 15:21:11 +0100
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Nov 07, 2019 at 02:46:53PM +0200, Georgi Djakov wrote:
> Hi Greg,
> This is a pull request with interconnect patches for the 5.5 merge window.
> All patches have been for a while in linux-next without reported issues. The
> details are in the signed tag. Please consider pulling into char-misc-next.

I don't know about
0003-interconnect-Disallow-interconnect-core-to-be-built-.patch here.
Shouldn't you just fix up the dependancies of subsystems that rely on
this?  We are moving more and more to kernels that "just work" with
everything as modules, even on arm64 systems.  So forbiding the
interconnect code from being able to be built as a module does not feel
good to me at all.

Same for
0007-interconnect-Remove-unused-module-exit-code-from-cor.patch, we are
adding module_init/exit() calls to modules, do not remove them!

Can you drop those two patches and resend?  Or I can just take these out
of the pull request and apply the rest as patches for now, if that's
easier for you to handle.


greg k-h

  reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 12:46 Georgi Djakov
2019-11-07 14:21 ` Greg Kroah-Hartman [this message]
2019-11-07 15:42   ` Georgi Djakov
2019-11-08 10:39     ` Greg Kroah-Hartman
2019-11-08 11:44       ` Georgi Djakov
2019-11-09  1:36       ` Bjorn Andersson
2019-11-09  8:48         ` Greg Kroah-Hartman
2019-11-09 20:27           ` Bjorn Andersson
2019-11-10 10:16             ` Greg Kroah-Hartman
2019-11-11  4:54               ` Viresh Kumar
2019-11-11  5:26                 ` Greg Kroah-Hartman
2019-11-14  8:41               ` Viresh Kumar
2019-11-14 12:59                 ` Georgi Djakov

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone