From: Wim Van Sebroeck <wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org>
To: Tobias Klauser <tklauser-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org>
Cc: nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 RESEND] watchdog: Add driver for Altera Watchdog Timer
Date: Fri, 1 Jul 2011 10:31:22 +0200 [thread overview]
Message-ID: <20110701083122.GA8678@infomag.iguana.be> (raw)
In-Reply-To: <20110614134859.GP20966-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org>
Hi Tobias,
> > I presume this will go in together with the other nios2 architecture patches?
>
> It will probably take some time until we get to the point where we're
> ready to submit nios2 arch patches. We started out with individual
> drivers to get used to the submission and review process. Most of them
> got taken by the respective subsystem maintainers.
>
> So if you want to take the driver through your tree, please go ahead.
> Otherwise I will resubmit it once we're ready to submit the nios2 arch.
Just let me know when you are ready to submit the nios2 arch and then I will do
the necessary on my side. In the mean time I will add your driver to the
linux-2.6-watchdog-next tree in some form, but I might convert the driver first
to the generic watchdog framework.
Kind regards,
Wim.
prev parent reply other threads:[~2011-07-01 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 15:19 [PATCH v3 RESEND] watchdog: Add driver for Altera Watchdog Timer Tobias Klauser
[not found] ` <1300461573-12268-1-git-send-email-tklauser-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org>
2011-05-27 8:23 ` Wim Van Sebroeck
[not found] ` <20110527082309.GB16394-flHiHfN8CTwhDM6iD19NGrNAH6kLmebB@public.gmane.org>
2011-06-14 13:48 ` Tobias Klauser
[not found] ` <20110614134859.GP20966-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org>
2011-07-01 8:31 ` Wim Van Sebroeck [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=20110701083122.GA8678@infomag.iguana.be \
--to=wim-iqzoog9ftrqzqb+pc5nmwq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org \
--cc=tklauser-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).