From: Ralf Baechle <ralf@linux-mips.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Michael Buesch <mb@bu3sch.de>,
matthieu castet <castet.matthieu@free.fr>,
linux-mips@linux-mips.org, netdev@vger.kernel.org
Subject: Re: [PATCH] bc47xx : export ssb_watchdog_timer_set
Date: Wed, 20 May 2009 08:15:13 +0100 [thread overview]
Message-ID: <20090520071513.GB24231@linux-mips.org> (raw)
In-Reply-To: <20090519173503.GD2691@tuxdriver.com>
On Tue, May 19, 2009 at 01:35:03PM -0400, John W. Linville wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Tue, 19 May 2009 13:35:03 -0400
> To: Michael Buesch <mb@bu3sch.de>
> Cc: Ralf Baechle <ralf@linux-mips.org>,
> matthieu castet <castet.matthieu@free.fr>,
> linux-mips@linux-mips.org, netdev@vger.kernel.org
> Subject: Re: [PATCH] bc47xx : export ssb_watchdog_timer_set
> Content-Type: text/plain; charset=us-ascii
>
> On Tue, May 19, 2009 at 07:29:20PM +0200, Michael Buesch wrote:
> > On Tuesday 19 May 2009 19:09:57 Ralf Baechle wrote:
> > > Maybe because I felt drivers/ssb/ was outside my jurisdiction - and unlike
> > > what alot of people may seem to think I'm not a full time MIPS kernel
> > > hacker.
> >
> > Ok nice.
> >
> > > I can deal with SSB patch if you so desire - but I have no experience with
> > > SSB, so I'd have somebody to rubberstamp non-trivial SSB patches before I
> > > queue them up.
> >
> > **Fwoo..
> > [stamp here]
> > ..mppp**
> >
> >
> > Done. :)
> >
> > > I can keep them either in the usual MIPS trees on
> > > linux-mips.org or I could create a separate linux-ssb tree, depending on
> > > what seems to be sensible. Also, reading the entry in the maintainers
> > > file I wonder if netdev is really the list of a choice?
> >
> > Yes it is, because the bus is only used on networking devices.
> > (Ethernet cards, wireless cards, and network routers)
> > I don't think you need to create a separate tree. ssb is pretty mature. There
> > won't be that many patches.
>
> OK, now I'm confused again -- should I take SSB patches, or is Ralf
> going to do it? :-)
My decoder ring says, I'll do it from now on :)
Cheers,
Ralf
next prev parent reply other threads:[~2009-05-20 7:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 22:10 [PATCH] bc47xx : export ssb_watchdog_timer_set matthieu castet
2009-05-18 22:41 ` John W. Linville
2009-05-19 13:24 ` Michael Buesch
2009-05-19 17:09 ` Ralf Baechle
2009-05-19 17:29 ` Michael Buesch
2009-05-19 17:35 ` John W. Linville
2009-05-20 7:15 ` Ralf Baechle [this message]
2009-05-20 12:57 ` John W. Linville
2009-05-20 13:49 ` Michael Buesch
2009-05-21 10:45 ` matthieu castet
2009-05-19 13:22 ` Michael Buesch
2009-05-21 10:39 ` matthieu castet
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=20090520071513.GB24231@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=castet.matthieu@free.fr \
--cc=linux-mips@linux-mips.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.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).