mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH] MIPS, IRQCHIP: Move i8259 irqchip driver to drivers/irqchip.
Date: Wed, 8 Jul 2015 15:13:18 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1507081512140.5134@nanos> (raw)
In-Reply-To: <20150708130149.GT18167@linux-mips.org>

On Wed, 8 Jul 2015, Ralf Baechle wrote:
> On Wed, Jul 08, 2015 at 02:57:38PM +0200, Thomas Gleixner wrote:
> 
> > >  arch/mips/Kconfig           |   4 -
> > >  arch/mips/kernel/Makefile   |   1 -
> > >  arch/mips/kernel/i8259.c    | 384 --------------------------------------------
> > >  drivers/irqchip/Kconfig     |   4 +
> > >  drivers/irqchip/Makefile    |   1 +
> > >  drivers/irqchip/irq-i8259.c | 383 +++++++++++++++++++++++++++++++++++++++++++
> > >  6 files changed, 388 insertions(+), 389 deletions(-)
> > 
> > Should I carry it, or want you merge it via the mips tree?
> > 
> > In the latter case: Acked-by-me.
> 
> I guess the conflict potencial will be lower if you carry it - and if
> somebody wants to merge it with one of the other i8259.c littered through
> the tree it probably also is better if you carry it.

Good point. That move might be just the trigger for me to sit down and
do it :)

Thanks,

	tglx

  reply	other threads:[~2015-07-08 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 12:46 Ralf Baechle
2015-07-08 12:57 ` Thomas Gleixner
2015-07-08 13:01   ` Ralf Baechle
2015-07-08 13:13     ` Thomas Gleixner [this message]
2015-07-08 13:45 ` Sergei Shtylyov
2015-07-08 16:38 ` Sergei Shtylyov

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=alpine.DEB.2.11.1507081512140.5134@nanos \
    --to=tglx@linutronix.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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

all inboxes | Powered by JetHome®