From: Andrew Morton <akpm@linux-foundation.org>
To: Andy Gross <agross@codeaurora.org>
Cc: "Stephen Boyd" <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-soc@vger.kernel.org,
linux-mips@linux-mips.org, "Hauke Mehrtens" <hauke@hauke-m.de>,
"Paul Walmsley" <paul@pwsan.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Bjorn Andersson" <bjorn.andersson@sonymobile.com>
Subject: Re: [PATCH v2 0/3] Add __ioread32_copy() and use it
Date: Thu, 17 Sep 2015 14:44:55 -0700 [thread overview]
Message-ID: <20150917144455.8b414be4f89688bbdca39692@linux-foundation.org> (raw)
In-Reply-To: <20150917214218.GA6003@qualcomm.com>
On Thu, 17 Sep 2015 16:42:18 -0500 Andy Gross <agross@codeaurora.org> wrote:
> > ho hum. I think I'll go with plan B: merge just "lib: iomap_copy: Add
> > __ioread32_copy()" and send that into Linus promptly. That way you
> > guys can sort out the driver patches in the usual fashion.
> >
>
> I just pulled in the original 8 patches and rebased. My plans were to stage
> those in linux-next through my for-next. Then add those on top just like you
> specified. But i could go either way.
OK, please do that.
WARNING: multiple messages have this Message-ID (diff)
From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Add __ioread32_copy() and use it
Date: Thu, 17 Sep 2015 14:44:55 -0700 [thread overview]
Message-ID: <20150917144455.8b414be4f89688bbdca39692@linux-foundation.org> (raw)
In-Reply-To: <20150917214218.GA6003@qualcomm.com>
On Thu, 17 Sep 2015 16:42:18 -0500 Andy Gross <agross@codeaurora.org> wrote:
> > ho hum. I think I'll go with plan B: merge just "lib: iomap_copy: Add
> > __ioread32_copy()" and send that into Linus promptly. That way you
> > guys can sort out the driver patches in the usual fashion.
> >
>
> I just pulled in the original 8 patches and rebased. My plans were to stage
> those in linux-next through my for-next. Then add those on top just like you
> specified. But i could go either way.
OK, please do that.
next prev parent reply other threads:[~2015-09-17 21:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 19:02 [PATCH v2 0/3] Add __ioread32_copy() and use it Stephen Boyd
2015-09-17 19:02 ` Stephen Boyd
2015-09-17 19:02 ` [PATCH v2 1/3] lib: iomap_copy: Add __ioread32_copy() Stephen Boyd
2015-09-17 19:02 ` Stephen Boyd
2015-09-17 19:02 ` [PATCH v2 2/3] soc: qcom: smd: Use __ioread32_copy() instead of open-coding it Stephen Boyd
2015-09-17 19:02 ` Stephen Boyd
2015-09-17 19:02 ` Stephen Boyd
2015-09-17 19:02 ` [PATCH v2 3/3] FIRMWARE: bcm47xx_nvram: Use __ioread32_copy() instead of open-coding Stephen Boyd
2015-09-17 19:02 ` Stephen Boyd
2015-09-22 16:29 ` Ralf Baechle
2015-09-22 16:29 ` Ralf Baechle
2015-09-17 19:56 ` [PATCH v2 0/3] Add __ioread32_copy() and use it Andrew Morton
2015-09-17 19:56 ` Andrew Morton
2015-09-17 21:42 ` Andy Gross
2015-09-17 21:42 ` Andy Gross
2015-09-17 21:44 ` Andrew Morton [this message]
2015-09-17 21:44 ` Andrew Morton
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=20150917144455.8b414be4f89688bbdca39692@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-soc@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sboyd@codeaurora.org \
--cc=zajec5@gmail.com \
/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.