From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fbdev@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] staging: sm750fb: avoid conflicting vesafb
Date: Tue, 20 Jun 2017 21:41:22 +0100 [thread overview]
Message-ID: <20170620204122.GA5603@sudip-laptop> (raw)
In-Reply-To: <20170620202055.zhleonjxyzzrl5d3@mwanda>
Hi Dan,
On Tue, Jun 20, 2017 at 11:20:55PM +0300, Dan Carpenter wrote:
> That's totally bogus. Just say you don't know. It's never a
> reguirement that people fix AMD drivers before they can review code...
Yes, I don't know how drm drivers work, so I blindly follow what has
been done there. And since sm750 ultimately has to be converted to a drm
driver to be taken out of staging, so I will prefer to have similar
changes here.
--
Regards
Sudip
next prev parent reply other threads:[~2017-06-20 20:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 20:32 [PATCH 1/2] staging: sm750fb: avoid conflicting vesafb Sudip Mukherjee
2017-06-19 20:32 ` [PATCH 2/2] staging: sm750fb: change default screen resolution Sudip Mukherjee
2017-06-19 20:47 ` [PATCH 1/2] staging: sm750fb: avoid conflicting vesafb Andy Shevchenko
2017-06-20 20:08 ` Sudip Mukherjee
2017-06-20 20:20 ` Dan Carpenter
2017-06-20 20:40 ` Andy Shevchenko
2017-06-20 20:44 ` Sudip Mukherjee
2017-06-20 20:41 ` Sudip Mukherjee [this message]
2017-06-25 12:43 ` Sudip Mukherjee
2017-06-25 12:54 ` Greg Kroah-Hartman
2017-06-25 13:54 ` Sudip Mukherjee
2017-06-25 14:27 ` Greg Kroah-Hartman
2017-06-25 15:07 ` Sudip Mukherjee
[not found] ` <31608A86C142F84E93092EC1B170B676743012DD@TWMBS01.tw.smi.ad>
2017-06-29 12:57 ` 答复: " Greg Kroah-Hartman
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=20170620204122.GA5603@sudip-laptop \
--to=sudipm.mukherjee@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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 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).