From: Sylvain Rochet <sylvain.rochet@finsecur.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"wim@iguana.be" <wim@iguana.be>
Subject: Re: [PATCH] watchdog: at91sam9: keep watchdog running in idle mode
Date: Sun, 16 Oct 2016 22:39:21 +0200 [thread overview]
Message-ID: <20161016203921.aq2iffthlowncisa@finsecur.com> (raw)
In-Reply-To: <59c665f8-de09-c11c-f62a-5064016cd8fd@roeck-us.net>
Hi Guenter,
On Sun, Oct 16, 2016 at 08:55:41AM -0700, Guenter Roeck wrote:
> On 10/16/2016 08:50 AM, Guenter Roeck wrote:
> > On 10/16/2016 08:33 AM, Sylvain Rochet wrote:
> > >
> > > Looks like this one falls through the cracks, it didn't reach mainline
> > > and therefore wasn't applied to stable branches.
> >
> > Possibly that happened because you did not copy the watchdog mailing list.
>
> ... and your other patches were not sent to the watchdog mailing list either,
> so you should not expect them to be picked up either.
>
> Seriously, how do you expect _any_ patch to be picked up if you neither copy
> the subsystem mailing list nor the subsystem maintainer ?
Whoops, thanks for the heads up, I wonder how I managed to mess up that
at that time, I usually take care of that. The other series need
respinning anyway so I can fix it for v2 (if any).
Cheers,
Sylvain
prev parent reply other threads:[~2016-10-16 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 20:28 Sylvain Rochet
2015-10-07 11:01 ` Alexandre Belloni
2016-10-16 15:33 ` Sylvain Rochet
2016-10-16 15:50 ` Guenter Roeck
2016-10-16 15:55 ` Guenter Roeck
2016-10-16 20:39 ` Sylvain Rochet [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-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=20161016203921.aq2iffthlowncisa@finsecur.com \
--to=sylvain.rochet@finsecur.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=stable@vger.kernel.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®