From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexander Holler <holler@ahsoftware.de>
Cc: STAGING SUBSYSTEM <devel@driverdev.osuosl.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Benjamin Valentin <benpicco@zedat.fu-berlin.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add exFAT driver
Date: Wed, 25 Sep 2013 13:21:52 -0700 [thread overview]
Message-ID: <20130925202151.GA6149@kroah.com> (raw)
In-Reply-To: <52433978.9050302@ahsoftware.de>
On Wed, Sep 25, 2013 at 09:28:56PM +0200, Alexander Holler wrote:
> Am 25.09.2013 20:45, schrieb Greg Kroah-Hartman:
> > On Wed, Sep 25, 2013 at 07:32:36PM +0100, Matthew Garrett wrote:
> >> On Wed, Sep 25, 2013 at 10:27:04AM -0700, Greg Kroah-Hartman wrote:
> >>
> >>> Who did you contact at Samsung? I'll be visiting there in a week so I
> >>> can try to track some people done in person. I really want their
> >>> signed-off-by: on the patch, as it is their code to start with, and it's
> >>> a bit rude to not get their approval for the code to be merged.
> >>
> >> It's arguably rude, but it's fine under the certificate of origin.
> >
> > Oh, I totally agree, just trying to be nice here. If a company objects
> > to having their code included in the tree, we should always take that
> > into consideration, especially given the ability for others to maintain
> > it. We've done this for years, nothing new here at all.
>
> Maybe a silly question, but isn't exFAT protected by some MS owned
> patents which might drive Linux users into the hand of MS lawyers as
> already happened with FAT? It would make me wonder if not. Maybe you
> could ask Samsung about that too, when you are there.
Because Samsung released the code under the GPLv2, and their lawyers
understand what that means, should answer any question you might have
about this.
thanks,
greg k-h
next prev parent reply other threads:[~2013-09-25 20:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 10:46 [PATCH] add exFAT driver Benjamin Valentin
2013-08-30 11:08 ` Vyacheslav Dubeyko
2013-08-30 15:42 ` Greg Kroah-Hartman
2013-09-25 16:36 ` Benjamin Valentin
2013-09-25 16:59 ` Anca Emanuel
2013-09-25 17:27 ` Greg Kroah-Hartman
2013-09-25 18:32 ` Matthew Garrett
2013-09-25 18:45 ` Greg Kroah-Hartman
2013-09-25 19:28 ` Alexander Holler
2013-09-25 20:21 ` Greg Kroah-Hartman [this message]
2013-09-25 20:43 ` Alexander Holler
2013-09-25 21:44 ` Anton Altaparmakov
2013-09-25 22:00 ` Alexander Holler
2013-09-25 22:10 ` Greg Kroah-Hartman
2013-09-25 22:29 ` Alexander Holler
2013-09-25 22:53 ` Matthew Garrett
2013-09-26 7:54 ` Anton Altaparmakov
2013-09-26 10:41 ` Dan Carpenter
2013-09-26 10:48 ` Alexander Holler
2013-09-26 11:06 ` Dan Carpenter
2013-09-26 7:50 ` Anton Altaparmakov
2013-09-25 21:57 ` Benjamin Valentin
2013-09-25 22:11 ` 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=20130925202151.GA6149@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benpicco@zedat.fu-berlin.de \
--cc=devel@driverdev.osuosl.org \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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.