From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] tc: Error handling clean-ups
Date: Mon, 27 Oct 2014 01:16:37 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.11.1410270102540.21390@eddie.linux-mips.org> (raw)
In-Reply-To: <20141027101017.6af4e810@canb.auug.org.au>
Stephen, Andrew --
> > I posted this fix originally to linux-mips@linux-mips.org back in April,
> > but it got lost and I don't want to give Ralf more stuff to handle than
> > absolutely necessary, he is really busy these days. Can you please take
> > it directly to linux-next then? There's nothing specific to MIPS in this
> > code really.
>
> I don't take patches directly into linux-next (unless they are very
> specific bug fixes for things that affect my builds - and even then I
> only keep them until a maintainer picks them up).
Good to know, will remember, thanks, and apologies to bother you then.
As the maintainer of this bus subsystem I wasn't sure what to do given
the situation.
> Sorry. You could try sending it to Linus or Andrew Morton.
Andrew, can you please take the change from the LKML message heading
this thread, or shall I resend it somehow for you to pick it up? This
doesn't really fit anywhere.
Thanks,
Maciej
next prev parent reply other threads:[~2014-10-27 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.11.1404062030280.15266@eddie.linux-mips.org>
2014-10-26 15:22 ` Maciej W. Rozycki
2014-10-26 23:10 ` Stephen Rothwell
2014-10-27 1:16 ` Maciej W. Rozycki [this message]
2014-10-27 1:38 ` Ralf Baechle
2014-10-27 13:41 ` Maciej W. Rozycki
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=alpine.LFD.2.11.1410270102540.21390@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
/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
Powered by JetHome