public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Mike Turquette <mturquette@ti.com>,
	Greg Ungerer <gerg@uclinux.org>,
	Julia Lawall <julia.lawall@lip6.fr>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: Make the managed clk functions generically available
Date: Mon, 10 Sep 2012 01:39:13 +0100	[thread overview]
Message-ID: <20120910003913.GM13739@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120910002020.GB16249@opensource.wolfsonmicro.com>

On Mon, Sep 10, 2012 at 08:20:21AM +0800, Mark Brown wrote:
> On Mon, Sep 10, 2012 at 01:15:24AM +0100, Russell King - ARM Linux wrote:
> > Note that the patch system doesn't always return error messages anymore
> > (it used to do that reliably, but as it's now a favourite target for
> > spammers and was creating soo much backscatter, which was then filling
> > my mailbox with bounces... that had to change.)
> 
> Hrm, that's not ideal.  It'd be nice if it were able to do something
> like always reply if there were patch contents, or if it found things
> like the KernelVersion line in there.  Obviously e-mail is also not time
> guaranteed so deciding it's not responded (and then working out why it
> did that) is going to be unreliable too.

It tries to - if it finds what it thinks is a patch in the right place
in the email.  If it doesn't think it found a patch then it won't reply.
In other words, if you include a patch without a PATCH FOLLOWS or the ---
commit message/diffstat break marker preceding it, it will ignore you.

> I do recall seeing the patch in the database but it's not showing up any
> more so perhaps I was thinking of a different patch.

Well, no patch ever gets deleted from the database... the only way even I
can do that is to manually issue the SQL.

> OK, that's what I'd thought was going on - it was the fact that you'd
> just acked the patch rather than asked for it to go to the patch tracker
> or something which made me wonder if things had changed.

I kind'a forgot because it's been soo long since I took any of those
patches...

  reply	other threads:[~2012-09-10  0:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1347202862-1617-1-git-send-email-lars@metafoo.de>
2012-09-09 20:57 ` [PATCH] clk: Make the managed clk functions generically available Russell King - ARM Linux
2012-09-09 23:50 ` Mark Brown
     [not found] ` <20120909235059.GA2643@sirena.org.uk>
2012-09-10  0:15   ` Russell King - ARM Linux
2012-09-10  0:20     ` Mark Brown
2012-09-10  0:39       ` Russell King - ARM Linux [this message]
2012-09-11 14:44         ` Lars-Peter Clausen
     [not found]         ` <504F4E36.20309@metafoo.de>
2012-09-11 14:50           ` Artem Bityutskiy
2012-09-12  1:32             ` Greg Ungerer
2012-09-12 20:43               ` Lars-Peter Clausen
     [not found]               ` <5050F3DB.1050202@metafoo.de>
2012-09-15 21:31                 ` Russell King - ARM Linux
2012-09-16  0:15                   ` Greg Ungerer
2012-09-18  8:00                   ` Thierry Reding
2012-09-18  9:35                     ` Russell King - ARM Linux
     [not found]                     ` <20120918093536.GV12245@n2100.arm.linux.org.uk>
2012-09-18 11:25                       ` Thierry Reding
2012-09-18 20:40                         ` Russell King - ARM Linux
     [not found]                         ` <20120918204014.GY12245@n2100.arm.linux.org.uk>
2012-09-19  6:55                           ` Thierry Reding
2012-09-11 17:51           ` Russell King - ARM Linux
2012-09-10  3:10 ` Greg Ungerer
2012-09-09 15:01 Lars-Peter Clausen

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=20120910003913.GM13739@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dedekind1@gmail.com \
    --cc=gerg@uclinux.org \
    --cc=julia.lawall@lip6.fr \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=mturquette@ti.com \
    /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