From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"alan@linux.intel.com" <alan@linux.intel.com>
Subject: Re: [PATCH v2] serial/8250_dw: use platform_get_irq() instead of platform_get_resource()
Date: Tue, 03 Mar 2015 17:59:34 +0200 [thread overview]
Message-ID: <1425398374.14897.155.camel@linux.intel.com> (raw)
In-Reply-To: <1425397657.17965.28.camel@synopsys.com>
On Tue, 2015-03-03 at 15:47 +0000, Alexey Brodkin wrote:
> > > For example it was useful for me when debugging stacked interrupt
> > > controllers setup - I got explicitly notified why this particular device
> > > failed on probe.
> >
> > There are so many device drivers which prints similar message that you
> > would consider to make a separate patch to platform.c code to do that
> > stuff there once for all.
> Then we may want to do another massive clean-up because there're lots of
> other drivers that have this message in some form :)
Yeah, you may do that and it will be (by my opinion) more useful than
introducing one more place with the duplicate message.
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
prev parent reply other threads:[~2015-03-03 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 15:11 [PATCH v2] serial/8250_dw: use platform_get_irq() instead of platform_get_resource() Alexey Brodkin
2015-03-03 15:26 ` Andy Shevchenko
2015-03-03 15:33 ` Alexey Brodkin
2015-03-03 15:43 ` Andy Shevchenko
2015-03-03 15:47 ` Alexey Brodkin
2015-03-03 15:59 ` Andy Shevchenko [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=1425398374.14897.155.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.