Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Johannes Thumshirn <johannes.thumshirn@men.de>
Cc: Wim Van Sebroeck <wim@iguana.be>, linux-watchdog@vger.kernel.org
Subject: Re: [GIT PULL v2] watchdog updates for Linux 3.13
Date: Wed, 23 Oct 2013 09:47:36 -0700	[thread overview]
Message-ID: <20131023164736.GA22394@roeck-us.net> (raw)
In-Reply-To: <20131023065759.GA24193@jtlinux>

On Wed, Oct 23, 2013 at 08:57:59AM +0200, Johannes Thumshirn wrote:
> On Tue, Oct 22, 2013 at 05:35:41PM -0700, Guenter Roeck wrote:
> > * PGP Signed by an unknown key
> >
> > Hi Wim,
> >
> > This is v2 of my pull request. Please ignore the previous request.
> > There are a couple of changes as outlined below, and I rebased the
> > branch to 3.12-rc6.
> >
> > Please consider pulling watchdog updates for Linux 3.13 from signed tag:
> >
> >     git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git watchdog-for-wim
> >
> > The tag has been applied on top of the watchdog-next branch. The branch includes
> > a number of patches I collected over the last few months. It does not include
> > all submitted patches; only the ones I reviewed and felt comfortable with are
> > included.
> >
> > I reviewed all patches and ran build tests as well as source verification tests
> > with both smatch and spatch. The branch has been on my Linux repo for a while,
> > so presumably Fenguang's robot will have built the code as well.
> > The w83627hf patches have been running on several servers for more than a month
> > without problems.
> >
> > You can find the most recent build results at
> > http://server.roeck-us.net:8010/builders/watchdog-next.
> >
> > If you don't want to apply the entire series, please consider applying whatever
> > subset you might feel comfortable with.
> >
> > Thanks,
> > Guenter
> >
> > ------
> 
> Hi Gunther,
> 
> Can you please drop the patch from me from the pull request?  I'm afraid
> something went wrong there, I thought Stephen Warren and I decided to just move
> the binding document and not change the bindings, as the driver went upstream in
> 3.11.
> 
I ended up reverting your patch on top of my tree. Wim can either do the same
if/when he decides to pull the patches, or simply drop the patch before sending
his next pull request to Linus.

Thanks,
Guenter

  reply	other threads:[~2013-10-23 16:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23  0:35 [GIT PULL v2] watchdog updates for Linux 3.13 Guenter Roeck
2013-10-23  6:57 ` Johannes Thumshirn
2013-10-23 16:47   ` Guenter Roeck [this message]
2013-10-23 23:05   ` Guenter Roeck
2013-10-24  6:22     ` Johannes Thumshirn
2013-10-24 15:17       ` Guenter Roeck
2013-10-29  8:44         ` 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=20131023164736.GA22394@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=johannes.thumshirn@men.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox