From: Vinod Koul <vinod.koul@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org
Subject: Re: [GIT PULL] TTY/Serial patches for 4.1-rc1
Date: Wed, 22 Apr 2015 12:23:00 +0530 [thread overview]
Message-ID: <20150422065300.GI2738@intel.com> (raw)
In-Reply-To: <CA+55aFzeqhQ=oDMoOmw_Mr6rzKRLCWC8bL1LtyXv96f-+_AtXA@mail.gmail.com>
On Tue, Apr 21, 2015 at 09:41:22AM -0700, Linus Torvalds wrote:
> On Tue, Apr 21, 2015 at 3:10 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > TTY/Serial patches for 4.1-rc1
> >
> > Here's the big tty/serial driver update for 4.1-rc1.
>
> This causes Kconfig annoyances:
>
> High Speed UART DMA support (HSU_DMA) [N/m/y] (NEW)
> High Speed UART DMA PCI driver (HSU_DMA_PCI) [N/m/y/?] (NEW)
>
> I _just_ said "no, I don't want High Speed UART DMA support", so why
> did it then ask me "do you want the High Speed UART DMA PCI driver"?
>
> And no, there wasn't even a help-fext for that first question (and the
> second one I couldn't be arsed about, at that point I just went "well,
> f*ck you too").
>
> So at the very least, the wording doesn't make sense. Or maybe that
> PCI driver question should depend on the previous one? And can we
> please make sure that there are help text entries for new config
> options?
>
> I pulled it, but please people, make sure this gets fixed. Our config
> phase is probably _the_ most painful part of trying to get new people
> involved in compiling their own kernels, so we should consider good
> Kconfig language a priority. Lack of help-texts, and questions that
> are annoying and make no sense are *not* helpful.
Agree, sorry about this.
This HSU_DMA shouldn't even be a user selectable symbol, they should be
selected the HSU_PCI driver (which has a help text) and this already done by
HSU_PCI
Linus,
Please apply this for fixing it. I have noticed few other places as well, will add
them on my dmaengine pull request and send.
Thanks
~Vinod
--><8----------><8----------------
From: Vinod Koul <vinod.koul@intel.com>
Date: Wed, 22 Apr 2015 12:17:46 +0530
Subject: [PATCH] dmaengine: hsu: don't prompt for hsu_core part
HSU_DMA is selected by the HSU_DMA_PCI driver, this should be user selected
so remove the user prompt for this
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
---
drivers/dma/hsu/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/hsu/Kconfig b/drivers/dma/hsu/Kconfig
index 7e98eff7440e..2810dca70612 100644
--- a/drivers/dma/hsu/Kconfig
+++ b/drivers/dma/hsu/Kconfig
@@ -1,6 +1,6 @@
# DMA engine configuration for hsu
config HSU_DMA
- tristate "High Speed UART DMA support"
+ tristate
select DMA_ENGINE
select DMA_VIRTUAL_CHANNELS
--
1.7.9.5
prev parent reply other threads:[~2015-04-22 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 10:10 [GIT PULL] TTY/Serial patches for 4.1-rc1 Greg KH
2015-04-21 16:41 ` Linus Torvalds
2015-04-22 6:53 ` Vinod Koul [this message]
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=20150422065300.GI2738@intel.com \
--to=vinod.koul@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=torvalds@linux-foundation.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