From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: doubt about sm7xxfb
Date: Wed, 11 Feb 2015 12:36:36 +0800 [thread overview]
Message-ID: <20150211043636.GA27598@kroah.com> (raw)
In-Reply-To: <20150210140747.GA15593@sudip-PC>
On Tue, Feb 10, 2015 at 07:37:47PM +0530, Sudip Mukherjee wrote:
> Hi Greg,
> we have this sm7xxfb in drivers/staging now which is supporting SM710,
> SM712, SM721 and SM722. I am also working on another new hardware
> SM750, which will be ready for staging in next 1 -2 weeks.
> this SM750 is entirely different hardware and these two drivers will
> have nothing in common.
Then make a new driver!
But why would a new driver go into staging? Anything new you create
should just go into the "correct" part of the kernel. Don't waste your
time on staging.
thanks,
greg k-h
next prev parent reply other threads:[~2015-02-11 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 14:07 doubt about sm7xxfb Sudip Mukherjee
2015-02-11 4:36 ` Greg Kroah-Hartman [this message]
2015-02-11 6:28 ` Sudip Mukherjee
2015-02-11 6:33 ` Greg Kroah-Hartman
2015-02-25 12:30 ` Sudip Mukherjee
2015-02-25 15:34 ` 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=20150211043636.GA27598@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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