From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Wim Van Sebroeck <wim@iguana.be>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>
Subject: Re: [GIT PULL REQUEST] watchdog - v4.15 Fixes
Date: Sun, 17 Dec 2017 12:32:39 -0800 [thread overview]
Message-ID: <ba3e337e-6442-b1fe-cab9-c0a863c35015@roeck-us.net> (raw)
In-Reply-To: <CAADWXX-_k5z=08P6sW_6xip+9SEyv+FmfCFFB2P+ux0=FDBeDw@mail.gmail.com>
On 12/17/2017 12:12 PM, Linus Torvalds wrote:
> Once more, gmail hated you. No real indication why, apart from:
>
> Why is this message in Spam? We've found that lots of messages from
> iguana.be are spam.
>
> I have no idea why that site is so hated, but one option that your
> upstream ISP is some scumbag place that allows spammers and scammers
> and thus the addresses end up being on some blacklist.
>
> Also, all of these commits were committed less than an hour before
> sending me the pull request, so I question the kind of testing they
> got..
>
The patches have been in -next for a while, only Wim moved them
into a different branch to be able to send you a pull request.
In -next:
8e1828d605df watchdog: hpwdt: SMBIOS check
ee11fc2b6e73 watchdog: indydog: Add dependency on SGI_HAS_INDYDOG
bff862153935 watchdog: Fix kref imbalance seen if handle_boot_enabled=0
01cd17d9fe08 watchdog: Fix potential kref imbalance when opening watchdog
You might as well blame me since I asked Wim to either send those patches
to you or to let me do it, and I would have pulled the patches from Wim's
watchdog-next repository (or from linux-next) as well.
Guenter
next prev parent reply other threads:[~2017-12-17 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 10:55 Wim Van Sebroeck
2017-12-17 20:12 ` Linus Torvalds
2017-12-17 20:32 ` Guenter Roeck [this message]
2017-12-17 21:20 ` Linus Torvalds
2017-12-25 17:10 ` Wim Van Sebroeck
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=ba3e337e-6442-b1fe-cab9-c0a863c35015@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®