All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: linux-next: manual merge of the tiny tree with the tip tree
Date: Wed, 29 Oct 2014 08:52:09 -0700	[thread overview]
Message-ID: <20141029155209.GA7287@thin> (raw)
In-Reply-To: <20140923083603.GA31876@gmail.com>

On Tue, Sep 23, 2014 at 10:36:03AM +0200, Ingo Molnar wrote:
> * Josh Triplett <josh@joshtriplett.org> wrote:
> > I've dropped tiny/no-io from tiny/next; I'll poke at it further 
> > and resubmit for the x86 tree later, likely not for the next 
> > merge window at this point.
> > 
> > Thanks for the feedback on process; this is day 1 of having a 
> > merge-window-bound tree in -next for the first time. :)
> 
> Sorry about the harshness of my initial email - I was unsure 
> about the background and we are close to the merge window. I have 
> no objections against the -tiny tree in linux-next, it's a good 
> effort.
> 
> I think we could cut down on the #ifdef uglies if we made the 
> ioperm callback pointer unconditional. That's just a tiny amount 
> of extra bloat, but should remove half of the #ifdefs or so? The 
> rest of the patches look fine.

I've revised the patch to eliminate quite a few #ifdefs, and in
particular almost all of those in .c files, by adding a macro
INIT_SET_IOPL_MASK to use in place of the initializer for set_iopl_mask,
and using __maybe_unused rather than wrapping function definitions in
#ifdef.  I'll send a new version momentarily.

> Usually hpa handles the x86 ioperm area, but he's swamped right 
> now, so I'll look at picking them up once you have submitted the 
> latest version. If you send it in the next day or two then they 
> could make the v3.18 merge window.

Other things came up (LinuxCon / Plumbers), but hopefully the new
version can go into 3.19.

- Josh Triplett

  reply	other threads:[~2014-10-29 15:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  4:32 linux-next: manual merge of the tiny tree with the tip tree Stephen Rothwell
2014-09-23  5:43 ` Ingo Molnar
2014-09-23  6:21   ` Josh Triplett
2014-09-23  8:36     ` Ingo Molnar
2014-10-29 15:52       ` Josh Triplett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-25  6:03 Stephen Rothwell
2014-11-25  6:16 ` Ingo Molnar
2014-11-25  6:16   ` Ingo Molnar
2014-11-25  6:30   ` John Stultz
2014-11-25  7:20     ` Josh Triplett
2014-11-25  6:48   ` Josh Triplett
2014-11-25 10:10     ` Ingo Molnar
2014-11-26  0:04       ` josh
2014-12-08 11:09         ` Ingo Molnar
2014-09-26  6:45 Stephen Rothwell
2014-09-23  4:23 Stephen Rothwell

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=20141029155209.GA7287@thin \
    --to=josh@joshtriplett.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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.