All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next <linux-next@vger.kernel.org>, mingo <mingo@redhat.com>
Subject: getting fixmap patches in linux-next
Date: Wed, 11 Dec 2013 10:25:05 -0500	[thread overview]
Message-ID: <1386775505.1979.105.camel@deneb.redhat.com> (raw)

Hi, I have cleanup of fixmap.h here:

 http://lkml.org/lkml/2013/11/25/474

Most of the series has been ack'd with the notable exception
of the arch/x86 part. I'd like to get this series into linux-next
but I'm not sure of the best way. I could put it in the c6x tree
but it doesn't belong there and I don't want to put the x86 patch
in there without any acks. I've cc'd Ingo thinking the tip tree
may be the place it should go.

--Mark

             reply	other threads:[~2013-12-11 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 15:25 Mark Salter [this message]
2013-12-11 15:40 ` getting fixmap patches in linux-next Ingo Molnar
2013-12-11 15:55   ` Mark Salter
2013-12-11 20:37     ` Stephen Rothwell
2013-12-11 22:01     ` Andrew Morton
2013-12-12 15:11       ` Mark Salter

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=1386775505.1979.105.camel@deneb.redhat.com \
    --to=msalter@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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.