From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@lst.de>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul@pwsan.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the generic-ioremap tree with the risc-v tree
Date: Mon, 18 Nov 2019 07:51:49 +0100 [thread overview]
Message-ID: <20191118065149.GA4850@lst.de> (raw)
In-Reply-To: <20191118174501.73050c78@canb.auug.org.au>
On Mon, Nov 18, 2019 at 05:45:01PM +1100, Stephen Rothwell wrote:
> 0c3ac28931d5 ("riscv: separate MMIO functions into their own header file")
As already mentioned in reply to this patch when it was posted I think
this kinda of split is a very bad idea.
next prev parent reply other threads:[~2019-11-18 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 6:45 linux-next: manual merge of the generic-ioremap tree with the risc-v tree Stephen Rothwell
2019-11-18 6:51 ` Christoph Hellwig [this message]
2019-11-19 18:33 ` Paul Walmsley
2019-11-19 18:33 ` Paul Walmsley
-- strict thread matches above, loose matches on Subject: below --
2019-11-18 6:30 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=20191118065149.GA4850@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul@pwsan.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.