From: Michael Jones <michael.jones@matrix-vision.de>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] OMAP3 clock: remove obsolete comment
Date: Fri, 27 Jul 2012 09:05:53 +0200 [thread overview]
Message-ID: <50123DD1.4090307@matrix-vision.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1207261349350.14468@utopia.booyaka.com>
Hi Paul,
On 07/26/2012 09:55 PM, Paul Walmsley wrote:
>
> Hello Michael,
>
> thanks for the patch. I've queued it for 3.7 after writing a changelog.
> Two minor comments for future patches: we don't accept patches with a
> non-null changelog - usually just something brief works fine. Also Tony
> wants all OMAP patches to be cc'ed to the linux-arm-kernel mailing list.
>
> regards,
>
> - Paul
Thanks for the comments, I'll adhere to them in the future. I assume you
meant you _only_ accept patches with a non-null changelog. I referred to
http://omappedia.org/wiki/Releasing_to_Linux_kernel_using_patches_and_emails
before my submission, and didn't see these two points. A few Q's:
Can I add these two points to that Wiki page? Or is there a more
authoritative checklist somewhere?
Why is it queued for 3.7? I thought 3.6 was in the works?
Where is it queued?
thanks,
Michael
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Erhard Meier
WARNING: multiple messages have this Message-ID (diff)
From: michael.jones@matrix-vision.de (Michael Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP3 clock: remove obsolete comment
Date: Fri, 27 Jul 2012 09:05:53 +0200 [thread overview]
Message-ID: <50123DD1.4090307@matrix-vision.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1207261349350.14468@utopia.booyaka.com>
Hi Paul,
On 07/26/2012 09:55 PM, Paul Walmsley wrote:
>
> Hello Michael,
>
> thanks for the patch. I've queued it for 3.7 after writing a changelog.
> Two minor comments for future patches: we don't accept patches with a
> non-null changelog - usually just something brief works fine. Also Tony
> wants all OMAP patches to be cc'ed to the linux-arm-kernel mailing list.
>
> regards,
>
> - Paul
Thanks for the comments, I'll adhere to them in the future. I assume you
meant you _only_ accept patches with a non-null changelog. I referred to
http://omappedia.org/wiki/Releasing_to_Linux_kernel_using_patches_and_emails
before my submission, and didn't see these two points. A few Q's:
Can I add these two points to that Wiki page? Or is there a more
authoritative checklist somewhere?
Why is it queued for 3.7? I thought 3.6 was in the works?
Where is it queued?
thanks,
Michael
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Erhard Meier
next prev parent reply other threads:[~2012-07-27 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 12:28 [PATCH] OMAP3 clock: remove obsolete comment Michael Jones
2012-07-26 19:55 ` Paul Walmsley
2012-07-26 19:55 ` Paul Walmsley
2012-07-27 7:05 ` Michael Jones [this message]
2012-07-27 7:05 ` Michael Jones
2012-07-27 7:14 ` Paul Walmsley
2012-07-27 7:14 ` Paul Walmsley
2012-07-27 7:28 ` Michael Jones
2012-07-27 7:28 ` Michael Jones
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=50123DD1.4090307@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.