From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] kernel.h: Move sysfs related macro to sysfs.h
Date: Fri, 3 Jun 2022 22:52:51 +0300 [thread overview]
Message-ID: <Yppmk94fTWCM3NjZ@smile.fi.intel.com> (raw)
In-Reply-To: <20220603121511.78aa66b02376d02557c29819@linux-foundation.org>
On Fri, Jun 03, 2022 at 12:15:11PM -0700, Andrew Morton wrote:
> On Fri, 3 Jun 2022 20:21:01 +0300 Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>
> > As stated in the comment of VERIFY_OCTAL_PERMISSIONS() it's related to sysfs.
> > Move it to the corresponding header.
>
> arm allmodconfig:
Thanks
x86 builds :(
I will look into it later on.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-06-03 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 17:21 [PATCH v1 1/1] kernel.h: Move sysfs related macro to sysfs.h Andy Shevchenko
2022-06-03 19:15 ` Andrew Morton
2022-06-03 19:52 ` Andy Shevchenko [this message]
2022-06-05 21:53 ` kernel test robot
2022-06-05 22:13 ` kernel test robot
2022-06-05 22:13 ` kernel test robot
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=Yppmk94fTWCM3NjZ@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.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