public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Tomas Pilar <tpilar@solarflare.com>
Cc: devel@edk2.groups.io, Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-platforms][PATCH 1/1] SfcPkg: Add new package
Date: Thu, 17 Oct 2019 18:18:58 +0100	[thread overview]
Message-ID: <20191017171858.GZ25504@bivouac.eciton.net> (raw)
In-Reply-To: <5cc83e67-5271-7f87-6188-ae4fa03e33ed@solarflare.com>

First of all, could you respin this to align more with what's
described in
https://github.com/tianocore/edk2-platforms/blob/about/Readme.md
?

Specifically, it should be visible from the Readme.md (not just the
Maintainers.txt history) who owns the branch (you).

Secondly, I would prefer SolarFlarePkg - the one redeeming factor of
CamelCase is that it eliminates guessing.

Some Bikeshedding and nitpicking below:

On Thu, Oct 17, 2019 at 05:19:44PM +0100, Tomas Pilar wrote:
> This package is for Solarflare Communications drivers and utilities.
> 
> Signed-off-by: Tomas Pilar <tpilar@solarflare.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> ---
>  Drivers/SfcPkg/Readme.md | 11 +++++++++++
>  Maintainers.txt          |  4 ++++
>  Readme.md                |  7 +++++++
>  3 files changed, 22 insertions(+)
>  create mode 100644 Drivers/SfcPkg/Readme.md
> 
> diff --git a/Drivers/SfcPkg/Readme.md b/Drivers/SfcPkg/Readme.md
> new file mode 100644
> index 0000000000..b26b0bbc8c
> --- /dev/null
  > +++ b/Drivers/SfcPkg/Readme.md
> @@ -0,0 +1,11 @@
> +Drivers and utilities for Solarflare Communications network adapters
> +
> +## Contact
> +
> +* [Website] (www.solarflare.com)
> +* [Support] (support@solarflare.com)

Umm...
Is your support department aware that they are now supporting an
in-progress version of an open source UEFI driver?

> +
> +## Licence
> +
> +The contents are licenced under BSD-2-Clause-Patent licence. +See top level
> Licence.txt in the edk2-platforms repository.

Link to it, markdown-style.

> \ No newline at end of file

*cough*

> diff --git a/Maintainers.txt b/Maintainers.txt
> index 1260c8d246..a293e7ebaa 100644
> --- a/Maintainers.txt
> +++ b/Maintainers.txt
> @@ -52,6 +52,10 @@ M: Leif Lindholm <leif.lindholm@linaro.org>
>  M: Ard Bieshuevel <ard.bieshuevel@linaro.org>
>  R: Andy Hayes <andy.hayes@displaylink.com>
>  +Drivers/SfcPkg

How did that happen? The '+' should have one fewer indent.
Preferably add a blank line before this section.

> +M: Leif Lindholm <leif.lindholm@linaro.org>
> +R: Tomas Pilar <tpilar@solarflare.com>
> +
>  Platform
>  M: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>  M: Leif Lindholm <leif.lindholm@linaro.org>
> diff --git a/Readme.md b/Readme.md
> index 2b54b8e0b4..4de427bc69 100644
> --- a/Readme.md
> +++ b/Readme.md
> @@ -247,6 +247,13 @@ For more information, see the
>  ## Socionext
>  * [SynQuacer](Platform/Socionext/DeveloperBox)
>  +# IHV Drivers

More weird indentation.
Ah:
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0

Yeah, you need to submit patches with git send-email. I'll also take
them on a publicly accessible branch, as long as the email copy isn't
badly enough corrupted that it complicates review.

Best Regards,

Leif

> +
> +These are independent hardware vendor products currently supported by
> +fimware, drivers and utilities in this tree.
> +
> +## Solarflare Communications
> +
>  # Maintainers
>   See [Maintainers.txt](Maintainers.txt).
> -- 
> 2.21.0
> 

      reply	other threads:[~2019-10-17 17:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 16:19 [edk2-platforms][PATCH 1/1] SfcPkg: Add new package Tomas Pilar (tpilar)
2019-10-17 17:18 ` Leif Lindholm [this message]

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-list 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=20191017171858.GZ25504@bivouac.eciton.net \
    --to=devel@edk2.groups.io \
    /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