From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-fbdev@vger.kernel, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, dan.carpenter@oracle.com
Subject: Re: [PATCH 1/2] staging: sm750fb: remove 750LE code
Date: Thu, 19 Mar 2015 15:15:39 +0100 [thread overview]
Message-ID: <20150319141539.GD7046@kroah.com> (raw)
In-Reply-To: <20150319140328.GA31838@sudip-PC>
On Thu, Mar 19, 2015 at 07:33:28PM +0530, Sudip Mukherjee wrote:
> On Thu, Mar 19, 2015 at 02:22:36PM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Mar 19, 2015 at 06:47:40PM +0530, Sudip Mukherjee wrote:
> > > 750LE is a special version of the hardware with Ip Core and
> > > Silicon Motion is making this hardware only for Huawei. It is not
> > > available to anyone else.
> >
> > And Huawei doesn't run Linux? (hint, they do...)
> >
> > Why remove this if someone can use it? I don't understand.
>
> this is part of my conversation with Teddy Wang of Silicon Motion:
> "I think you can remove it . SM750LE is a special version. And it's
> just a IP core. No one except huawei will use it."
>
> and moreover I donot have that 750LE hardware to test any changes.
> I just have the SM712 and SM750 hardware. so ....
>
> now, whatever you decide .. I will surely like to have the code in
> place.
I suggest to leave it, it's not costing anything to keep around, and I
think you removed additional code with this patch anyway, which wasn't
good...
thanks,
greg k-h
next prev parent reply other threads:[~2015-03-19 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 13:17 [PATCH 1/2] staging: sm750fb: remove 750LE code Sudip Mukherjee
2015-03-19 13:17 ` [PATCH 2/2] staging: sm750fb: fix build warning Sudip Mukherjee
2015-03-19 13:22 ` [PATCH 1/2] staging: sm750fb: remove 750LE code Greg Kroah-Hartman
2015-03-19 14:03 ` Sudip Mukherjee
2015-03-19 14:15 ` Greg Kroah-Hartman [this message]
2015-03-19 14:28 ` Sudip Mukherjee
2015-03-19 13:28 ` Dan Carpenter
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=20150319141539.GD7046@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-fbdev@vger.kernel \
--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