From: Greg KH <gregkh@linuxfoundation.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
"Ramirez Luna, Omar" <omar.ramirez@ti.com>,
"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
Jiri Kosina <jkosina@suse.cz>,
Felipe Contreras <felipe.contreras@nokia.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] staging: tidspbridge: enable watchdog by default
Date: Fri, 10 Feb 2012 08:16:57 -0800 [thread overview]
Message-ID: <20120210161657.GA4162@kroah.com> (raw)
In-Reply-To: <CAMP44s29yn-vYThbr6cDsvvFgKVELW1nA=onkkVHwp4h2yi_hQ@mail.gmail.com>
On Fri, Feb 10, 2012 at 06:05:59PM +0200, Felipe Contreras wrote:
> > From 5c7ad6c00d051d5444474007cdbecdf14bf3d0cb Mon Sep 17 00:00:00 2001
> > From: "Justin P. Mattock" <justinmattock@gmail.com>
> > Date: Fri, 10 Feb 2012 07:19:45 -0800
> > Subject: [PATCH] Add dependency TIDSBRIDGE_WDT3 to TIDSBRIDGE.
> >
> > This would add the missing _dependency_ to tidsbridge to prevent a warning from happening.
> >
> > Note: my Kconfig skills are not the greatest so the below may or may not work.
> > I can't test this because I dont have the hardware.
>
> Your patch *always* turns on TIDSPBRIDGE_WDT3, which is not what we
> want. Depending on the firmware, some people might want it off.
What firmware? Why not document this properly somewhere in the help
entries? Why not detect this automatically in the kernel based on the
firmware version?
> Basically, right now on the typical firmware, people have to either
> manually turn TIDSPBRIDGE_WDT3 on, or they will see the warning.
So, for the "typical" firmware, you do want this on, so the patch makes
sense.
How about the code be fixed so that it doesn't generate this type of
warning when using the "typical" firmware, instead of having to rely on
confusing Kconfig entries.
Still confused,
greg k-h
next prev parent reply other threads:[~2012-02-10 16:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 1:01 [PATCH] staging: tidspbridge: enable watchdog by default Felipe Contreras
2012-02-01 1:12 ` Greg KH
2012-02-01 1:37 ` Felipe Contreras
2012-02-01 3:22 ` Justin P. Mattock
2012-02-01 8:11 ` Felipe Contreras
2012-02-01 20:22 ` Ramirez Luna, Omar
2012-02-01 3:44 ` Greg KH
2012-02-01 7:26 ` Felipe Contreras
2012-02-09 17:35 ` Greg KH
2012-02-09 18:41 ` Felipe Contreras
2012-02-09 18:43 ` Felipe Contreras
2012-02-09 18:59 ` Greg KH
2012-02-09 23:30 ` Felipe Contreras
2012-02-10 0:45 ` Ramirez Luna, Omar
2012-02-10 5:18 ` Greg KH
2012-02-10 15:35 ` Justin P. Mattock
2012-02-10 16:05 ` Felipe Contreras
2012-02-10 16:14 ` Justin P. Mattock
2012-02-10 16:16 ` Greg KH [this message]
2012-02-10 16:29 ` Felipe Contreras
2012-02-10 16:16 ` Felipe Contreras
2012-02-10 17:48 ` Greg KH
2012-02-14 1:12 ` Ramirez Luna, Omar
2012-02-10 18:00 ` Dan Carpenter
2012-02-10 19:42 ` Felipe Contreras
2012-02-10 20:35 ` Dan Carpenter
2012-02-10 20:43 ` Felipe Contreras
[not found] ` <CAB-zwWhSoiMNVGQ=u=6-Umte-AaP9Qih8QMJFTyk8pjXaXysLg@mail.gmail.com>
2012-02-11 23:03 ` Felipe Contreras
2012-02-14 1:06 ` Ramirez Luna, Omar
2012-02-14 16:23 ` Felipe Contreras
2012-02-15 2:56 ` Ramirez Luna, Omar
2012-02-15 9:43 ` Víctor M. Jáquez L.
2012-02-15 11:41 ` Felipe Contreras
2012-02-15 12:02 ` Víctor M. Jáquez L.
2012-02-15 22:32 ` Omar Ramirez Luna
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=20120210161657.GA4162@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=felipe.contreras@gmail.com \
--cc=felipe.contreras@nokia.com \
--cc=jkosina@suse.cz \
--cc=justinmattock@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@ti.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;
as well as URLs for NNTP newsgroup(s).