[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YmA4ILK5Gv/Gdaso@kroah.com>
Date: Wed, 20 Apr 2022 18:43:12 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Bruno Moreira-Guedes <codeagain@...eagain.dev>
Cc: Martyn Welch <martyn@...chs.me.uk>,
Manohar Vanga <manohar.vanga@...il.com>,
linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org,
outreachy@...ts.linux.dev,
Bruno's Patch Watchbox <patch-reply@...eagain.dev>
Subject: Re: [PATCH v2 2/3] staging: vme: Add VME_BUS dependency to Kconfig
On Mon, Apr 18, 2022 at 08:39:29PM -0300, Bruno Moreira-Guedes wrote:
> Please, disregard the following message as there's a typo in the prefix.
>
> On Mon, Apr 18, 2022 at 08:31:09PM -0300, Bruno Moreira-Guedes wrote:
> > The KConfig file for VME_USER ('drivers/staging/vme/devices/Kconfig')
> > sourced at "drivers/vme/boards/KConfig" misses a `depends on` line for
> > VME_BUS, which is unnoticeable for menuconfig users who aren't be able
> > to select it through this interface without setting the CONFIG_VME_BUS
> > option because it's nested on VME_BUS menu entry.
> ...
> > VME windows in a manner at least semi-compatible with the interface
> > --
> > 2.35.3
> >
>
> It's already sent a new copy with the proper version number. Nothing's
> changed except for the message ID and the v2 typo.
I can't handle 2 v2 of this same commit, our tools get very confused (as
do people.) Would you be able to unwind this if you were in my
position?
Please resubmit a v3 of this series with everything fixed up.
thanks,
greg k-h
Powered by blists - more mailing lists