From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] kmod: bump to version 19
Date: Tue, 18 Nov 2014 14:21:23 +0100 [thread overview]
Message-ID: <20141118142123.47e08033@free-electrons.com> (raw)
In-Reply-To: <1416243576-42474-1-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Mon, 17 Nov 2014 16:59:36 +0000, Vicente Olivert Riera wrote:
> - Bump to version 19
> - Rename 0001 patch to follow the new name convention
> - Adapt the 0001 patch to the new version
> - Remove the already-upstreamed 0002 patch
> - Update the hash value
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Applied to next, thanks. After changing just one thing.
> diff --git a/package/kmod/kmod-0001-fix-O_CLOEXEC.patch b/package/kmod/0001-fix-O_CLOEXEC.patch
> similarity index 83%
> rename from package/kmod/kmod-0001-fix-O_CLOEXEC.patch
> rename to package/kmod/0001-fix-O_CLOEXEC.patch
> index 4861c57..e09372c 100644
> --- a/package/kmod/kmod-0001-fix-O_CLOEXEC.patch
> +++ b/package/kmod/0001-fix-O_CLOEXEC.patch
> @@ -1,3 +1,7 @@
> +Adapt this patch to version 19
> +
> +Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
I don't think this should go here, otherwise the patch isn't a proper
git patch anymore. Instead, I modified the commit log to add the fact
that you updated the patch to version 19, and added your SoB below
Thomas DS one.
See:
http://git.buildroot.net/buildroot/tree/package/kmod/0001-fix-O_CLOEXEC.patch?h=next.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-18 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 16:59 [Buildroot] [PATCH] kmod: bump to version 19 Vicente Olivert Riera
2014-11-18 13:21 ` Thomas Petazzoni [this message]
2014-11-18 13:26 ` Vicente Olivert Riera
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=20141118142123.47e08033@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.