From: Christoph Hellwig <hch@lst.de>
To: Nick Hu <nickhu@andestech.com>
Cc: Christoph Hellwig <hch@lst.de>,
green.hu@gmail.com, deanbo422@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] nds32: use get_kernel_nofault in dump_mem
Date: Thu, 28 Jan 2021 11:16:33 +0100 [thread overview]
Message-ID: <20210128101633.GA6249@lst.de> (raw)
In-Reply-To: <20200721112800.GA27356@lst.de>
On Tue, Jul 21, 2020 at 01:28:00PM +0200, Christoph Hellwig wrote:
> Can you pich the patches up in the nds32 tree for Linus? There are
> not short-term dependencies on them.
It seems like these patches are still sitting in linux-next and never
made it to Linus/
next prev parent reply other threads:[~2021-01-28 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 11:44 [PATCH 1/2] nds32: remove dump_instr Christoph Hellwig
2020-07-20 11:44 ` [PATCH 2/2] nds32: use get_kernel_nofault in dump_mem Christoph Hellwig
2020-07-21 11:07 ` Nick Hu
2020-07-21 11:28 ` Christoph Hellwig
2021-01-28 10:16 ` Christoph Hellwig [this message]
2021-02-24 7:47 ` Christoph Hellwig
2021-02-24 8:59 ` Greentime Hu
2021-02-24 9:02 ` Christoph Hellwig
2020-07-21 11:08 ` [PATCH 1/2] nds32: remove dump_instr Nick Hu
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=20210128101633.GA6249@lst.de \
--to=hch@lst.de \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickhu@andestech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox