Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] sunxi-mali-driver-mainline: new package
Date: Thu, 15 Feb 2018 23:32:58 +0100	[thread overview]
Message-ID: <87mv09lw85.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <979834e4-a338-525b-c7fd-1241c72127fb@micronovasrl.com> (Giulio Benetti's message of "Thu, 15 Feb 2018 23:06:28 +0100")

>>>>> "Giulio" == Giulio Benetti <giulio.benetti@micronovasrl.com> writes:

 > Hi,
 > Il 15/02/2018 23:03, Peter Korsgaard ha scritto:
 >>>>>>> "Giulio" == Giulio Benetti <giulio.benetti@micronovasrl.com> writes:
 >> 
 >> Hi,
 >> 
 >> > Thank you very much for helping me on this,
 >> > it was not so easy as first package to me.
 >> 
 >> You are welcome, thank you for contributing!
 >> 
 >> As you perhaps noticed, I've also bumped the sunxi-mali-mainline-driver
 >> version for 4.15 support:
 >> 
 >> https://git.busybox.net/buildroot/commit/?h=next&id=1d339809d61aeed2911291830581f643596a2e5c

 > Yes, I've seen, I'm almost trying to rebuild.
 > I've seen you use quilt before calling build.sh script.
 > But build.sh should call it by itself.

No, I'm NOT using quilt. quilt is not a required dependency for
Buildroot (and we don't have a host-quilt package), so I'm tweaking
build.sh to use our apply-patches.sh script like we use to apply our
patches instead of quilt.

 > Ah, one question, you figure as Author because you've reworked heavily
 > the patch, right? (and it seems more than right to me)
 > Or was it a mistake?

Ups, that was mistake. I wanted to keep you authorship for the 2
patches, but me for the version bump - But apparently git ends up
changing the authorship when you squash commits which I did to apply the
various fixups - Sorry about that!

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-02-15 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25 22:22 [Buildroot] [PATCH 1/2] sunxi-mali-driver-mainline: new package Giulio Benetti
2017-11-25 22:22 ` [Buildroot] [PATCH 2/2] sunxi-mali-mainline: " Giulio Benetti
2017-11-27 14:31   ` Maxime Ripard
2018-02-15 20:43   ` Peter Korsgaard
2018-02-15 20:51     ` Giulio Benetti
2017-11-27 14:28 ` [Buildroot] [PATCH 1/2] sunxi-mali-driver-mainline: " Maxime Ripard
2017-11-27 15:23   ` Giulio Benetti
2017-11-27 23:34     ` Giulio Benetti
2018-01-13 12:22       ` Giulio Benetti
2018-02-15 21:05 ` Peter Korsgaard
2018-02-15 21:34   ` Giulio Benetti
2018-02-15 22:03     ` Peter Korsgaard
2018-02-15 22:06       ` Giulio Benetti
2018-02-15 22:32         ` Peter Korsgaard [this message]
2018-02-15 22:35           ` Giulio Benetti
2018-02-16  9:20           ` Giulio Benetti
2018-02-16 12:26             ` Peter Korsgaard
2018-02-16 12:34               ` Giulio Benetti

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=87mv09lw85.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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