From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: akpm@linux-foundation.org, keescook@chromium.org,
peterz@infradead.org, gpiccoli@canonical.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] kernel.h: remove duplicate headers
Date: Thu, 7 May 2020 16:36:08 +0300 [thread overview]
Message-ID: <20200507133608.GV185537@smile.fi.intel.com> (raw)
In-Reply-To: <20200507131608.63373-1-chenzhou10@huawei.com>
On Thu, May 07, 2020 at 09:16:08PM +0800, Chen Zhou wrote:
> Remove duplicate headers which are included twice.
Thanks, this is included in my patch set to split out some parts of this header
to new headers.
(It basically removes all occurrences of div64.h)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-05-07 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 13:16 [PATCH -next] kernel.h: remove duplicate headers Chen Zhou
2020-05-07 13:36 ` Andy Shevchenko [this message]
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=20200507133608.GV185537@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=chenzhou10@huawei.com \
--cc=gpiccoli@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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