linux-kernel - Re: [PATCH v2] staging: board: Remove macro board

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <X/LkvTaT4+AV+tov@kroah.com>
Date:   Mon, 4 Jan 2021 10:49:49 +0100
From:   Greg KH <greg@...ah.com>
To:     "chensong_2000@....cn" <chensong_2000@....cn>
Cc:     linux-kernel@...r.kernel.org, geert@...ux-m68k.org,
        sfr@...b.auug.org.au, abbotti@....co.uk,
        hsweeten@...ionengravers.com
Subject: Re: [PATCH v2] staging: board: Remove macro board_staging

On Mon, Jan 04, 2021 at 05:17:52PM +0800, chensong_2000@....cn wrote:
> 
> 
> 在 2021/1/4 下午5:07, Greg KH 写道:
> > On Mon, Jan 04, 2021 at 04:55:46PM +0800, Song Chen wrote:
> > > Macro is not supposed to have flow control in it's
> > > statement, remove.
> > > 
> > > Signed-off-by: Song Chen <chensong_2000@....cn>
> > > 
> > > ---
> > > Changes in v2:
> > > 1, kzm9d_init and armadillo800eva_init are not compatible
> > > with the definition of device_initcall, fixed.
> > 
> > I already applied v1, so what am I supposed to do here?
> 
> In https://lore.kernel.org/lkml/20170220175506.GA30142@kroah.com/, it
> seems that kernel can live with the checkpatch warning messages of "Macro is
> not supposed to have flow control in it's statement" in
> driver/staging/board. If so, please drop the patch.

I'm confused, maybe I didn't apply the first patch?  Am I confusing this
with a different patch for this code?

greg "I need more coffee..." k-h