All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: trivial@kernel.org, linaro-kernel@lists.linaro.org,
	linux-kernel@vger.kernel.org,
	Hans Ulli Kroll <ulli.kroll@googlemail.com>,
	"moderated list:BLACKFIN RTC DRIVER"
	<adi-buildroot-devel@lists.sourceforge.net>,
	Alessandro Zummo <a.zummo@towertech.it>,
	"moderated list:ARM/CORTINA SYSTEMS GEMINI ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
	<rtc-linux@googlegroups.com>
Subject: [rtc-linux] Re: [PATCH V1 Resend 06/10] drivers: rtc: Drop (un)likely before IS_ERR(_OR_NULL)
Date: Wed, 12 Aug 2015 16:16:25 +0530	[thread overview]
Message-ID: <20150812104625.GB20238@linux> (raw)
In-Reply-To: <20150812104133.GE3411@piout.net>

On 12-08-15, 12:41, Alexandre Belloni wrote:
> Hi Viresh,
> 
> Why are you resending?

I never got a reply from Andrew Morton on V1, so resent it again. And
today Andrew asked me to take this via trivial tree.

So the resent.

I need to find a sane way to get few more people to the cover-letter.
The problem is that I am generating the cc-list with get_maintainers,
and if I combine that list for all the patches, it becomes huge. And
really can't send the cover-letter to those people then. Few lists may
block it as well, due to high number of cc'd people.

I am telling this because, the cover-letter did contain the reason for
resend.

-- 
viresh

-- 
-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V1 Resend 06/10] drivers: rtc: Drop (un)likely before IS_ERR(_OR_NULL)
Date: Wed, 12 Aug 2015 16:16:25 +0530	[thread overview]
Message-ID: <20150812104625.GB20238@linux> (raw)
In-Reply-To: <20150812104133.GE3411@piout.net>

On 12-08-15, 12:41, Alexandre Belloni wrote:
> Hi Viresh,
> 
> Why are you resending?

I never got a reply from Andrew Morton on V1, so resent it again. And
today Andrew asked me to take this via trivial tree.

So the resent.

I need to find a sane way to get few more people to the cover-letter.
The problem is that I am generating the cc-list with get_maintainers,
and if I combine that list for all the patches, it becomes huge. And
really can't send the cover-letter to those people then. Few lists may
block it as well, due to high number of cc'd people.

I am telling this because, the cover-letter did contain the reason for
resend.

-- 
viresh

WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: trivial@kernel.org, linaro-kernel@lists.linaro.org,
	linux-kernel@vger.kernel.org,
	Hans Ulli Kroll <ulli.kroll@googlemail.com>,
	"moderated list:BLACKFIN RTC DRIVER" 
	<adi-buildroot-devel@lists.sourceforge.net>,
	Alessandro Zummo <a.zummo@towertech.it>,
	"moderated list:ARM/CORTINA SYSTEMS GEMINI ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	"open list:REAL TIME CLOCK (RTC) SUBSYSTEM" 
	<rtc-linux@googlegroups.com>
Subject: Re: [PATCH V1 Resend 06/10] drivers: rtc: Drop (un)likely before IS_ERR(_OR_NULL)
Date: Wed, 12 Aug 2015 16:16:25 +0530	[thread overview]
Message-ID: <20150812104625.GB20238@linux> (raw)
In-Reply-To: <20150812104133.GE3411@piout.net>

On 12-08-15, 12:41, Alexandre Belloni wrote:
> Hi Viresh,
> 
> Why are you resending?

I never got a reply from Andrew Morton on V1, so resent it again. And
today Andrew asked me to take this via trivial tree.

So the resent.

I need to find a sane way to get few more people to the cover-letter.
The problem is that I am generating the cc-list with get_maintainers,
and if I combine that list for all the patches, it becomes huge. And
really can't send the cover-letter to those people then. Few lists may
block it as well, due to high number of cc'd people.

I am telling this because, the cover-letter did contain the reason for
resend.

-- 
viresh

  reply	other threads:[~2015-08-12 10:46 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 10:29 [PATCH V1 Resend 00/10] trivial: Drop unlikely before IS_ERR(_OR_NULL) Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 01/10] err.h: add (missing) unlikely() to IS_ERR_OR_NULL() Viresh Kumar
2015-10-07 10:35   ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 02/10] PM / OPP: Drop unlikely before IS_ERR(_OR_NULL) Viresh Kumar
2015-08-12 10:29   ` Viresh Kumar
2015-08-28 14:17   ` Rafael J. Wysocki
2015-08-28 13:52     ` Jiri Kosina
2015-08-28 14:30       ` Rafael J. Wysocki
2015-09-09  2:43       ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 03/10] drivers: devfreq: " Viresh Kumar
2015-08-12 10:29   ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 04/10] drivers: misc: " Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 05/10] drivers: net: " Viresh Kumar
2015-08-12 10:29 ` [rtc-linux] [PATCH V1 Resend 06/10] drivers: rtc: Drop (un)likely " Viresh Kumar
2015-08-12 10:29   ` Viresh Kumar
2015-08-12 10:29   ` Viresh Kumar
2015-08-12 10:41   ` [rtc-linux] " Alexandre Belloni
2015-08-12 10:41     ` Alexandre Belloni
2015-08-12 10:41     ` Alexandre Belloni
2015-08-12 10:46     ` Viresh Kumar [this message]
2015-08-12 10:46       ` Viresh Kumar
2015-08-12 10:46       ` Viresh Kumar
2015-08-12 11:42       ` [rtc-linux] " Alexandre Belloni
2015-08-12 11:42         ` Alexandre Belloni
2015-08-12 11:42         ` Alexandre Belloni
2015-08-12 11:47         ` [rtc-linux] " Viresh Kumar
2015-08-12 11:47           ` Viresh Kumar
2015-08-12 11:47           ` Viresh Kumar
     [not found] ` <cover.1439375087.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-12 10:29   ` [PATCH V1 Resend 07/10] fs: Drop unlikely " Viresh Kumar
2015-08-12 10:29     ` Viresh Kumar
2015-08-12 10:29     ` Viresh Kumar
2015-08-12 18:28     ` Jeff Layton
2015-08-20 16:08       ` Steve French
2015-08-20 16:08         ` Steve French
     [not found]         ` <CAH2r5mvUC2WO6sVqhe_QCgiCJbRbahDsSj=-Uzk7LB_peTqjLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-20 16:14           ` Viresh Kumar
2015-08-20 16:14             ` Viresh Kumar
2015-08-20 16:14             ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 08/10] blk-cgroup: " Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 09/10] mm: " Viresh Kumar
2015-08-12 10:29   ` Viresh Kumar
2015-08-12 10:29 ` [PATCH V1 Resend 10/10] net: " Viresh Kumar
2015-08-12 10:41   ` Viresh Kumar
2015-08-12 10:29   ` Viresh Kumar
2015-08-18  9:08 ` [PATCH V1 Resend 00/10] trivial: " Viresh Kumar

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=20150812104625.GB20238@linux \
    --to=viresh.kumar@linaro.org \
    --cc=a.zummo@towertech.it \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=trivial@kernel.org \
    --cc=ulli.kroll@googlemail.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.