From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>,
Alexander Duyck
<alexander.h.duyck-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org
Cc: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
jiangshanlai-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
pavel-+ZI9xUNit7I@public.gmane.org,
zwisler-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Subject: Re: [driver-core PATCH v5 5/9] driver core: Establish clear order of operations for deferred probe and remove
Date: Thu, 08 Nov 2018 15:42:19 -0800 [thread overview]
Message-ID: <1541720539.196084.236.camel@acm.org> (raw)
In-Reply-To: <499e4358e72fca510fa6fcfb76ea3ac3792db08f.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
On Tue, 2018-11-06 at 17:34 -0800, Joe Perches wrote:
> On Tue, 2018-11-06 at 15:48 -0800, Bart Van Assche wrote:
> > On Mon, 2018-11-05 at 13:12 -0800, Alexander Duyck wrote:
> > > One change I made in addition is I replaced the use of "bool X:1" to define
> > > the bitfield to a "u8 X:1" setup in order to resolve some checkpatch
> > > warnings.
> >
> > Please use "bool X:1" instead of "u8 X:1". I think it was a bad idea to make
> > checkpatch complain about "bool X:1" since "bool X:1" should only be avoided
> > in structures for which alignment must be architecture-independent. For struct
> > device it is fine if member alignment differs per architecture. Additionally,
> > changing "bool X:1" into "u8 X:1" will reduce performance on architectures that
> > cannot do byte addressing.
>
> I generally agree. But the checkpatch warning _could_
> be useful in those cases where alignment should be
> architecture-independent.
>
> Any suggestion on how to improve the message?
It would be great if a heuristic could be developed that recognizes structs
for which the data layout must be architecture independent. If such a
heuristic could be developed it could be used to only display warn about
"bool X:n" for such structures.
Bart.
next prev parent reply other threads:[~2018-11-08 23:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 21:11 [driver-core PATCH v5 0/9] Add NUMA aware async_schedule calls Alexander Duyck
2018-11-05 21:11 ` [driver-core PATCH v5 4/9] driver core: Move async_synchronize_full call Alexander Duyck
[not found] ` <154145231976.29224.39638353241256116.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-06 1:04 ` Bart Van Assche
[not found] ` <1541466289.196084.176.camel-HInyCGIudOg@public.gmane.org>
2018-11-06 16:18 ` Alexander Duyck
[not found] ` <e2fec0e159757f31abbd258e284a844d0d8a2859.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-11-06 17:22 ` Bart Van Assche
[not found] ` <154145223352.29224.8912797012647157172.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-05 21:11 ` [driver-core PATCH v5 1/9] workqueue: Provide queue_work_node to queue work near a given NUMA node Alexander Duyck
[not found] ` <154145230445.29224.14651284855380723028.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-06 0:42 ` Bart Van Assche
[not found] ` <1541464948.196084.168.camel-HInyCGIudOg@public.gmane.org>
2018-11-06 16:27 ` Alexander Duyck
2018-11-05 21:11 ` [driver-core PATCH v5 2/9] async: Add support for queueing on specific " Alexander Duyck
[not found] ` <154145230954.29224.13087735653265580553.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-07 0:50 ` Bart Van Assche
2018-11-05 21:11 ` [driver-core PATCH v5 3/9] device core: Consolidate locking and unlocking of parent and device Alexander Duyck
2018-11-05 21:12 ` [driver-core PATCH v5 5/9] driver core: Establish clear order of operations for deferred probe and remove Alexander Duyck
[not found] ` <154145232484.29224.1635232599636954462.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-06 4:10 ` kbuild test robot
[not found] ` <201811061228.iteFLO2p%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-11-06 23:51 ` Bart Van Assche
2018-11-07 0:52 ` Alexander Duyck
[not found] ` <1541548274.196084.197.camel-HInyCGIudOg@public.gmane.org>
2018-11-23 1:23 ` Rong Chen
2018-11-23 14:19 ` Bart Van Assche
2018-11-06 23:48 ` Bart Van Assche
[not found] ` <1541548114.196084.195.camel-HInyCGIudOg@public.gmane.org>
2018-11-07 1:34 ` Joe Perches
[not found] ` <499e4358e72fca510fa6fcfb76ea3ac3792db08f.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2018-11-08 23:42 ` Bart Van Assche [this message]
2018-11-11 14:31 ` Pavel Machek
2018-11-27 2:35 ` Dan Williams
2018-11-27 16:49 ` Alexander Duyck
2018-11-05 21:12 ` [driver-core PATCH v5 6/9] driver core: Probe devices asynchronously instead of the driver Alexander Duyck
[not found] ` <154145232994.29224.4383053368766089653.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-07 0:22 ` Bart Van Assche
2018-11-05 21:12 ` [driver-core PATCH v5 7/9] driver core: Attach devices on CPU local to device node Alexander Duyck
[not found] ` <154145233508.29224.9891071445860629874.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-07 0:24 ` Bart Van Assche
2018-11-05 21:12 ` [driver-core PATCH v5 8/9] PM core: Use new async_schedule_dev command Alexander Duyck
[not found] ` <154145234017.29224.9183571187943571535.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-07 0:24 ` Bart Van Assche
2018-11-06 0:50 ` [driver-core PATCH v5 0/9] Add NUMA aware async_schedule calls Bart Van Assche
[not found] ` <1541465425.196084.170.camel-HInyCGIudOg@public.gmane.org>
2018-11-06 16:25 ` Alexander Duyck
2018-11-05 21:12 ` [driver-core PATCH v5 9/9] libnvdimm: Schedule device registration on node local to the device Alexander Duyck
[not found] ` <154145234526.29224.2575533246153120029.stgit-+uVpp3jiz/RcxmDmkzA3yGt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2018-11-07 0:26 ` Bart Van Assche
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=1541720539.196084.236.camel@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=alexander.h.duyck-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=jiangshanlai-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.org \
--cc=rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=zwisler-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).