All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: Additional patches in my watchdog-next branch
Date: Tue, 29 Dec 2015 08:02:08 -0800	[thread overview]
Message-ID: <20151229160208.GA30405@roeck-us.net> (raw)
In-Reply-To: <20151229072108.GB6292@spo001.leaseweb.nl>

Hi Wim,

On Tue, Dec 29, 2015 at 08:21:08AM +0100, Wim Van Sebroeck wrote:
> Hi Guenter,
> 
> > On Mon, Dec 28, 2015 at 11:54:27PM +0100, Wim Van Sebroeck wrote:
> > > Hi Guenter,
> > > 
> > > > On Mon, Dec 28, 2015 at 04:27:11PM +0100, Wim Van Sebroeck wrote:
> > > > > Hi Guneter,
> > > > > 
> > > > > > I have a number of patches pending in my watchdog-next branch which are not
> > > > > > in your watchdog-next repository. Below is a summary, rebased onto your
> > > > > > repository. This does not include the patches I had submitted.
> > > > > > 
> > > > > > Please consider those patches for v4.5.
> > > > > 
> > > > > I'm still working on those. Will be for this evening. I left those because they are all new drivers. I wanted to have all fixes and other patches first.
> > > > > So not finished yet :-) I will also add your dev fixes (V2 patchset containing 5 patches).
> > > > > 
> > > > Thanks!
> > > 
> > > No problem. I think we now have all patches that should go in for v4.5 .
> > > 
> > > There is off course still other stuff that I need to look at:
> > > SBSA, pretimeout, bcm63xx, stmp3xxx GETBOOTSTATUS (although I have the impression that this patch is a dead end because you cannot really tell what the reboot reason is with the patch), soft timer's moving into the core, mei watchdog code, ...
> > Hi Wim,
> > 
> > I'll have to look into those again as well. Most will now conflict
> > with the new watchdog core code.
> > 
> > Any thoughts on the other patch series I sent out, to create the watchdog
> > device in watchdog_dev.c, and to handle reference counting in the watchdog
> > core ? That would be a prerequisite for me to rebase (and rework) the soft
> > timer handling core. I had hoped that the changes to handle reference
> > counting in the core could make it into 4.5.
> 
> Need to review this 6-part patchset still. But probably still possible for 4.5 .

That would be great.

> The soft-timer patches are also 4.6 at the earliest.
> 
Absolutely agree. I'll have to rebase and retest the code.

Thanks,
Guenter

> Kind regards,
> Wim.
> 

  reply	other threads:[~2015-12-29 16:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 15:23 Additional patches in my watchdog-next branch Guenter Roeck
2015-12-28 15:27 ` Wim Van Sebroeck
2015-12-28 21:57   ` Guenter Roeck
2015-12-28 22:54     ` Wim Van Sebroeck
2015-12-28 23:17       ` Vladimir Zapolskiy
2015-12-29  7:17         ` Wim Van Sebroeck
2015-12-29 16:04           ` Guenter Roeck
2015-12-29 16:37             ` Thomas Petazzoni
2015-12-29 17:28               ` Guenter Roeck
2015-12-30  9:44                 ` Thomas Petazzoni
2015-12-30 13:30                   ` Fu Wei
2015-12-30 14:02                     ` Thomas Petazzoni
2015-12-30 15:01                       ` Fu Wei
2015-12-30 15:03                         ` Thomas Petazzoni
2015-12-30 15:06                           ` Fu Wei
2015-12-30 11:44                 ` Fu Wei
2015-12-30 11:30               ` Fu Wei
2016-01-03 22:49               ` Vladimir Zapolskiy
2015-12-29  0:08       ` Guenter Roeck
2015-12-29  7:21         ` Wim Van Sebroeck
2015-12-29 16:02           ` Guenter Roeck [this message]
2015-12-29 20:01             ` Wim Van Sebroeck
2015-12-29 21:20               ` Guenter Roeck
2015-12-30 10:06                 ` 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=20151229160208.GA30405@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-watchdog@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 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.