From: Dongjoo Seo <dseo3@uci.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: SeongJae Park <sj38.park@gmail.com>,
"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
acme@kernel.org, akpm@linux-foundation.org,
alexander.shishkin@linux.intel.com, amit@kernel.org,
benh@kernel.crashing.org, brendanhiggins@google.com,
corbet@lwn.net, david@redhat.com, dwmw@amazon.com,
elver@google.com, fan.du@intel.com, foersleo@amazon.de,
gthelen@google.com, guoju.fgj@alibaba-inc.com,
jgowans@amazon.com, joe@perches.com, linux-damon@amazon.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mgorman@suse.de, mheyne@amazon.de,
minchan@kernel.org, mingo@redhat.com, namhyung@kernel.org,
peterz@infradead.org, riel@surriel.com, rientjes@google.com,
rostedt@goodmis.org, rppt@kernel.org, shakeelb@google.com,
shuah@kernel.org, sieberf@amazon.com, sjpark@amazon.de,
snu@zelle79.org, vbabka@suse.cz, vdavydov.dev@gmail.com,
zgf574564920@gmail.com
Subject: Re: [PATCH v34 00/13] Introduce Data Access MONitor (DAMON)
Date: Fri, 23 Jul 2021 16:51:45 +0900 [thread overview]
Message-ID: <B0D5F589-1F50-4970-BEA7-9C213E6D9947@uci.edu> (raw)
In-Reply-To: <YPpwCS4CpGtJTy9t@kroah.com>
> On Jul 23, 2021, at 4:30 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
> http://daringfireball.net/2007/07/on_top
>
Sorry for the bad format email.
Thank you for your information. It really helps me with further mailing.
> On Fri, Jul 23, 2021 at 04:16:27PM +0900, Dongjoo Seo wrote:
>> Thank you for your comment!.
>>
>> It has been a long time since Nvidia ended supporting the new kernel
>> version on tx2 boards, but for researchers, this set of boards (tx2,
>> px2, agx) is a very attractive candidate to use.
>
> But why are you stuck at a known-buggy and insecure kernel version? I
> would work on fixing that first, before worrying about new features.
I need a board that has a GPU in my work.
However, Nvidia’s driver source code is not open-source.
I thought it would be easier to use the old compatible kernel with this tool than to use the Nvidia driver with one major version different kernel.
Thanks again for your advice on emailing!
Best
Dongjoo Seo
next prev parent reply other threads:[~2021-07-23 7:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 7:02 [PATCH v34 00/13] Introduce Data Access MONitor (DAMON) Dongjoo Seo
2021-07-23 7:08 ` Greg KH
2021-07-23 7:16 ` Dongjoo Seo
2021-07-23 7:30 ` Greg KH
2021-07-23 7:51 ` Dongjoo Seo [this message]
2021-07-23 8:30 ` SeongJae Park
2021-07-23 8:40 ` SeongJae Park
2021-07-26 13:32 ` SeongJae Park
-- strict thread matches above, loose matches on Subject: below --
2021-07-16 8:14 SeongJae Park
2021-07-27 21:30 ` Shakeel Butt
2021-07-28 8:36 ` SeongJae Park
2021-08-02 8:24 ` SeongJae Park
2021-08-04 7:41 ` SeongJae Park
2021-08-06 0:03 ` Andrew Morton
2021-08-06 11:48 ` SeongJae Park
2021-08-09 14:07 ` SeongJae Park
2021-08-06 0:43 ` Andrew Morton
2021-08-06 11:48 ` SeongJae Park
2021-08-07 18:28 ` 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=B0D5F589-1F50-4970-BEA7-9C213E6D9947@uci.edu \
--to=dseo3@uci.edu \
--cc=Jonathan.Cameron@huawei.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=amit@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dwmw@amazon.com \
--cc=elver@google.com \
--cc=fan.du@intel.com \
--cc=foersleo@amazon.de \
--cc=gregkh@linuxfoundation.org \
--cc=gthelen@google.com \
--cc=guoju.fgj@alibaba-inc.com \
--cc=jgowans@amazon.com \
--cc=joe@perches.com \
--cc=linux-damon@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mheyne@amazon.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=shuah@kernel.org \
--cc=sieberf@amazon.com \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.de \
--cc=snu@zelle79.org \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=zgf574564920@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).