From: Greg KH <gregkh@linuxfoundation.org>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: linux-kernel@vger.kernel.org,
Juan David Gonzalez Cobas <juan.david.gonzalez.cobas@cern.ch>,
"Emilio G. Cota" <cota@braap.org>,
Samuel Iglesias Gonsalvez <siglesias@igalia.com>
Subject: Re: [PATCH V2 0/2] FMC: resend sample drivers
Date: Tue, 18 Jun 2013 14:36:06 -0700 [thread overview]
Message-ID: <20130618213606.GA10816@kroah.com> (raw)
In-Reply-To: <cover.1371589927.git.rubini@gnudd.com>
On Tue, Jun 18, 2013 at 11:27:02PM +0200, Alessandro Rubini wrote:
> As suggested by Greg-KH [1] I'm resending the two example submodules
> (one carrier driver and one mezzanine driver) with a proper licence
> text for BSD. Among the various wordings, I chose the shortest one, as
> used by a number of drivers/net/wireless/ files. Thank you David for
> checking the distribution policies.
>
> I rebased to next-20130617 and rebuilt, with no conflicts. In any
> of the patches of the original series.
>
> [1] https://lkml.org/lkml/2013/6/17/772:
> "Just redo those two patches and send them as 'v2'")
>
> Alessandro Rubini (2):
> FMC: add a software carrier driver
> FMC: add a software mezzanine driver
Did I only not apply 2 patches? I thought there should be some more
that I'm missing here. Can you resend _everything_ that I need to apply
that I haven't already?
thanks,
greg k-h
next prev parent reply other threads:[~2013-06-18 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 21:27 [PATCH V2 0/2] FMC: resend sample drivers Alessandro Rubini
2013-06-18 21:27 ` [PATCH V2 1/2] FMC: add a software carrier driver Alessandro Rubini
2013-06-18 21:27 ` [PATCH V2 2/2] FMC: add a software mezzanine driver Alessandro Rubini
2013-06-18 21:36 ` Greg KH [this message]
2013-06-18 21:38 ` [PATCH V2 0/2] FMC: resend sample drivers Alessandro Rubini
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=20130618213606.GA10816@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cota@braap.org \
--cc=juan.david.gonzalez.cobas@cern.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.com \
--cc=siglesias@igalia.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 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.