From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 0/3] dropwatch: Post upgrade tweaks
Date: Thu, 2 Jul 2020 09:35:37 +0200 [thread overview]
Message-ID: <20200702073540.24100-1-ada@thorsis.com> (raw)
Hei hei,
I already had the version bump on my todo stack, but Michael was faster
with c03e3ff8f8f9 ("dropwatch: version bump 2015-07-06-g7c33d8a ->
1.5.3"). However I still had some leftovers and split them up now and
send this as a follow up series to the mentioned commit.
Greets
Alex
Alexander Dahl (3):
dropwatch: Update license information
dropwatch: Update help text
dropwatch: Add upstream patches
...ssue-when-compiling-with-Wcast-align.patch | 47 +++++++++++++++++++
.../0002-Fix-configure-for-libnl3-genl.patch | 43 +++++++++++++++++
patches/dropwatch-1.5.3/series | 5 ++
rules/dropwatch.in | 4 +-
rules/dropwatch.make | 3 +-
5 files changed, 99 insertions(+), 3 deletions(-)
create mode 100644 patches/dropwatch-1.5.3/0001-Fix-build-issue-when-compiling-with-Wcast-align.patch
create mode 100644 patches/dropwatch-1.5.3/0002-Fix-configure-for-libnl3-genl.patch
create mode 100644 patches/dropwatch-1.5.3/series
--
2.26.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2020-07-02 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 7:35 Alexander Dahl [this message]
2020-07-02 7:35 ` [ptxdist] [PATCH 1/3] dropwatch: Update license information Alexander Dahl
2020-07-06 6:31 ` [ptxdist] [APPLIED] " Michael Olbrich
2020-07-02 7:35 ` [ptxdist] [PATCH 2/3] dropwatch: Update help text Alexander Dahl
2020-07-06 6:31 ` [ptxdist] [APPLIED] " Michael Olbrich
2020-07-02 7:35 ` [ptxdist] [PATCH 3/3] dropwatch: Add upstream patches Alexander Dahl
2020-07-06 6:31 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20200702073540.24100-1-ada@thorsis.com \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
/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