From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
"Luis R . Rodriguez" <mcgrof@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Paul Bolle <pebolle@tiscali.nl>, Arnd Bergmann <arnd@arndb.de>,
Michal Simek <michal.simek@xilinx.com>,
Hans de Goede <j.w.r.degoede@gmail.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 02/11] video: fbdev: kconfig: Remove blank help text
Date: Tue, 13 Feb 2018 13:31:45 +0100 [thread overview]
Message-ID: <2836658.i9VlN9LAid@amdc3058> (raw)
In-Reply-To: <CAFkk2KQxPnwMKmvhCoKQ0BBciTc5JKqjJqHGHAMR5uHF0w13sg@mail.gmail.com>
On Thursday, February 01, 2018 05:56:18 PM Ulf Magnusson wrote:
> On Thu, Feb 1, 2018 at 4:52 PM, Bartlomiej Zolnierkiewicz
> <b.zolnierkie@samsung.com> wrote:
> >
> > Hi,
> >
> > On Wednesday, January 31, 2018 10:34:21 AM Ulf Magnusson wrote:
> >> Blank help texts are probably either a typo, a Kconfig misunderstanding,
> >> or some kind of half-committing to adding a help text (in which case a
> >> TODO comment would be clearer, if the help text really can't be added
> >> right away).
> >>
> >> Best to remove them, IMO.
> >
> > How about actually adding some meaningful help texts instead
> > (as a general rule each user visible option should have valid
> > help text)?
> >
> >> Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
> >> ---
> >> drivers/video/fbdev/Kconfig | 1 -
> >> 1 file changed, 1 deletion(-)
> >>
> >> diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
> >> index 6962b4583fd7..11e699f1062b 100644
> >> --- a/drivers/video/fbdev/Kconfig
> >> +++ b/drivers/video/fbdev/Kconfig
> >> @@ -1156,7 +1156,6 @@ config FB_I810_I2C
> >> bool "Enable DDC Support"
> >> depends on FB_I810 && FB_I810_GTF
> >> select FB_DDC
> >> - help
> >
> > Please add a missing help text instead (take a look at FB_SAVAGE_I2C
> > config option to see how a valid help text entry should look like).
>
> The FB_I810_I2C option was added in 74f6ae84b23 ("[PATCH] i810fb: Add
> i2c/DDC support"). What do you think about adding this bit from the
> commit message as the help text?
>
> Add DDC/I2C support for i810fb. This will allow the driver to get display
> information, especially for monitors with fickle timings.
Seems fine to me, please add:
If unsure, say Y.
and send it as a proper patch.
> I'm not familiar with this code, so I don't want to do too much
> guessing myself. :)
:)
> > In the longer term we should consider removing *_I2C config options
> > and just make the main config options always enable I2C subsystem
> > directly if needed/useful (some fbdev drivers are doing it this way
> > already).
> >
> >> config FB_LE80578
> >> tristate "Intel LE80578 (Vermilion) support"
> >
> > Best regards,
> > --
> > Bartlomiej Zolnierkiewicz
> > Samsung R&D Institute Poland
> > Samsung Electronics
> >
>
> Cheers,
> Ulf
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2018-02-13 12:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 9:34 [PATCH 00/11] Remove blank help texts from Kconfig files and add warning Ulf Magnusson
2018-01-31 9:34 ` [PATCH 01/11] net/sched: kconfig: Remove blank help texts Ulf Magnusson
2018-01-31 9:34 ` [PATCH 02/11] video: fbdev: kconfig: Remove blank help text Ulf Magnusson
2018-02-01 15:52 ` Bartlomiej Zolnierkiewicz
2018-02-01 16:56 ` Ulf Magnusson
2018-02-01 17:07 ` Masahiro Yamada
2018-02-13 12:31 ` Bartlomiej Zolnierkiewicz [this message]
2018-02-13 14:02 ` [PATCH] video: fbdev: kconfig: Add help text to FB_I810_I2C Ulf Magnusson
2018-03-12 15:08 ` Bartlomiej Zolnierkiewicz
2018-01-31 9:34 ` [PATCH 03/11] mmc: kconfig: Remove blank help text Ulf Magnusson
2018-02-01 17:09 ` Masahiro Yamada
2018-02-14 10:11 ` Ulf Hansson
2018-01-31 9:34 ` [PATCH 04/11] Staging: rtl8192u: " Ulf Magnusson
2018-02-01 17:09 ` Masahiro Yamada
2018-01-31 9:34 ` [PATCH 05/11] Staging: rtl8192e: " Ulf Magnusson
2018-02-01 17:09 ` Masahiro Yamada
2018-01-31 9:34 ` [PATCH 06/11] lib/Kconfig.debug: " Ulf Magnusson
2018-02-01 17:10 ` Masahiro Yamada
2018-01-31 9:34 ` [PATCH 07/11] MIPS: BCM63XX: kconfig: " Ulf Magnusson
2018-01-31 9:34 ` [PATCH 08/11] MIPS: " Ulf Magnusson
2018-02-01 17:11 ` Masahiro Yamada
2018-01-31 9:34 ` [PATCH 09/11] arm: vt8500: " Ulf Magnusson
2018-02-01 17:11 ` Masahiro Yamada
2018-01-31 9:34 ` [PATCH 10/11] nios2: " Ulf Magnusson
2018-02-01 17:11 ` Masahiro Yamada
2018-02-02 9:28 ` Ley Foon Tan
2018-01-31 9:34 ` [PATCH 11/11] kconfig: Warn if help text is blank Ulf Magnusson
2018-01-31 15:27 ` [PATCH 00/11] Remove blank help texts from Kconfig files and add warning Masahiro Yamada
2018-01-31 20:46 ` Randy Dunlap
2018-02-01 17:07 ` Masahiro Yamada
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=2836658.i9VlN9LAid@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.w.r.degoede@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=pebolle@tiscali.nl \
--cc=rdunlap@infradead.org \
--cc=ulfalizer@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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