From: Andrew Morton <akpm@linux-foundation•org>
To: Mark Salter <msalter@redhat•com>
Cc: Ingo Molnar <mingo@kernel•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next <linux-next@vger•kernel.org>, mingo <mingo@redhat•com>
Subject: Re: getting fixmap patches in linux-next
Date: Wed, 11 Dec 2013 14:01:57 -0800 [thread overview]
Message-ID: <20131211140157.0a9c6decb597b491968c484a@linux-foundation.org> (raw)
In-Reply-To: <1386777359.1979.106.camel@deneb.redhat.com>
On Wed, 11 Dec 2013 10:55:59 -0500 Mark Salter <msalter@redhat•com> wrote:
> On Wed, 2013-12-11 at 16:40 +0100, Ingo Molnar wrote:
> > * Mark Salter <msalter@redhat•com> wrote:
> >
> > > 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. [...]
> >
> > It didn't look controversial to me:
> >
> > Acked-by: Ingo Molnar <mingo@kernel•org>
> >
> > > [...] 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.
> >
> > I think akpm is usually collecting such generic arch and kmap patches
> > - mind pinging him whether he'd like to take it into -mm?
>
> Thanks, will do.
It seems that "[PATCH 03/11] arm: use generic fixmap.h" has issues?
If/when that gets resolved, please integrate all the reviewed-by's and
acked-by's and cc me on the resend?
next prev parent reply other threads:[~2013-12-11 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 15:25 getting fixmap patches in linux-next Mark Salter
2013-12-11 15:40 ` Ingo Molnar
2013-12-11 15:55 ` Mark Salter
2013-12-11 20:37 ` Stephen Rothwell
2013-12-11 22:01 ` Andrew Morton [this message]
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=20131211140157.0a9c6decb597b491968c484a@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@kernel$(echo .)org \
--cc=mingo@redhat$(echo .)com \
--cc=msalter@redhat$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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