From: "'Greg KH'" <gregkh@linuxfoundation.org>
To: hayeswang <hayeswang@realtek.com>
Cc: oliver@neukum.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
"'nic_swsd'" <nic_swsd@realtek.com>
Subject: Re: [PATCH v3 net-next] net/usb: new driver for RTL8152
Date: Thu, 2 May 2013 20:23:15 -0700 [thread overview]
Message-ID: <20130503032315.GA22077@kroah.com> (raw)
In-Reply-To: <4215C45C849149B8A86B57F8D603AAEA@realtek.com.tw>
On Fri, May 03, 2013 at 11:11:47AM +0800, hayeswang wrote:
> Greg KH [mailto:gregkh@linuxfoundation.org]
> > Sent: Friday, May 03, 2013 10:33 AM
> > To: Hayeswang
> > Cc: oliver@neukum.org; netdev@vger.kernel.org;
> > linux-kernel@vger.kernel.org; linux-usb@vger.kernel.org; nic_swsd
> > Subject: Re: [PATCH v3 net-next] net/usb: new driver for RTL8152
> >
> > On Fri, May 03, 2013 at 10:01:25AM +0800, Hayes Wang wrote:
> > > Add new driver for supporting Realtek RTL8152 Based USB 2.0
> > Ethernet Adapters
> > >
> > > Signed-off-by: Hayes Wang <hayeswang@realtek.com>
> > > Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>
> >
> > You removed the wording I had questions about last time, does
> > that mean
> > the previous wording was not correct, or that you no longer are
> > publicising the fact that this driver reads on some patents that you
> > own?
> >
> > You also failed to answer my previous questions, why?
>
> That description is about the patent for the hw design, not for
> software. It indicates that the design of the hw uses those patents
> from the other compnay. I have no idea about how to deal with those
> patents. What should I do for sending a patch?
That makes sense to me, removing it is correct. It's now up to the
netdev developers to accept this, thanks for the quick response.
greg k-h
next prev parent reply other threads:[~2013-05-03 3:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 8:45 [PATCH net-next] net/usb: new driver for RTL8152 Hayes Wang
2013-04-26 11:56 ` Oliver Neukum
[not found] ` <201305020622.r426MYGv032465@rtits1.realtek.com>
2013-05-02 7:46 ` hayeswang
2013-05-02 9:02 ` Oliver Neukum
2013-05-02 19:48 ` [PATCH v2 " Hayes Wang
2013-05-02 14:12 ` Greg KH
2013-05-02 17:32 ` David Miller
2013-05-03 2:01 ` [PATCH v3 " Hayes Wang
2013-05-03 2:33 ` Greg KH
2013-05-03 3:11 ` hayeswang
2013-05-03 3:23 ` 'Greg KH' [this message]
2013-05-03 4:00 ` David Miller
2013-05-06 20:17 ` David Miller
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=20130503032315.GA22077@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=oliver@neukum.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