All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Yushchenko <nyushchenko@dev.rtsoft.ru>
To: Lee Jones <lee.jones@linaro.org>
Cc: Grant Likely <grant.likely@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	lugovskoy@dev.rtsoft.ru
Subject: Re: [PATCH 11/21] mfd: use devm_irq_of_parse_and_map() where appropriate
Date: Wed, 18 Jun 2014 15:31:57 +0400	[thread overview]
Message-ID: <53A178AD.3060003@dev.rtsoft.ru> (raw)
In-Reply-To: <20140618084838.GR21030@lee--X1>

>> Hmm...  probably it was too early to apply this?  I was just going
>> to prepare v2, based on discussion...
>
> Which discussion?

One you are replying in?

https://lkml.org/lkml/2014/6/4/136

>> Also, applying only 11/21, without 01/21, will just cause build errors ...
>
> CC'ing me on this patch alone when you know you have build
> dependencies on other patches in the set is a bad idea.  Failing to
> mention that you wanted the patch to be handled in a special and/or
> unconventional way is an even worse idea.
>
> How are you expecting this patch(-set) to be handled?

Sorry but I did not CC you this patch.

I sent entire patchset to mailing lists and to maintainers of IRQ and 
device tree subsystems.
I used git send-email, and all mails went out to the same recipients.
Recipient addresses extracted using scripts/get_maintainer.pl applied to 
the "main" patch of the patchset.
I did not sent entire patchset to maintainers of individual changed 
drivers because this makes recipient address too big and too much looks 
like spamming.
I did not send individual patches to individual addresses to avoid cases 
of partially-applied patchset that will just break things (actually this 
is what happened with 11/21)

I'm quite sorry if I did things wrong, it was my first attempt to sent 
patchset with tree-wide fixes. However, I don't see what I've done 
wrong... any hints on that will be appreciated.

Nikita


WARNING: multiple messages have this Message-ID (diff)
From: Nikita Yushchenko <nyushchenko-jFhMxQ4mL6a2X5qOxWx28w@public.gmane.org>
To: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Grant Likely
	<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Benjamin Herrenschmidt
	<benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	lugovskoy-jFhMxQ4mL6a2X5qOxWx28w@public.gmane.org
Subject: Re: [PATCH 11/21] mfd: use devm_irq_of_parse_and_map() where appropriate
Date: Wed, 18 Jun 2014 15:31:57 +0400	[thread overview]
Message-ID: <53A178AD.3060003@dev.rtsoft.ru> (raw)
In-Reply-To: <20140618084838.GR21030@lee--X1>

>> Hmm...  probably it was too early to apply this?  I was just going
>> to prepare v2, based on discussion...
>
> Which discussion?

One you are replying in?

https://lkml.org/lkml/2014/6/4/136

>> Also, applying only 11/21, without 01/21, will just cause build errors ...
>
> CC'ing me on this patch alone when you know you have build
> dependencies on other patches in the set is a bad idea.  Failing to
> mention that you wanted the patch to be handled in a special and/or
> unconventional way is an even worse idea.
>
> How are you expecting this patch(-set) to be handled?

Sorry but I did not CC you this patch.

I sent entire patchset to mailing lists and to maintainers of IRQ and 
device tree subsystems.
I used git send-email, and all mails went out to the same recipients.
Recipient addresses extracted using scripts/get_maintainer.pl applied to 
the "main" patch of the patchset.
I did not sent entire patchset to maintainers of individual changed 
drivers because this makes recipient address too big and too much looks 
like spamming.
I did not send individual patches to individual addresses to avoid cases 
of partially-applied patchset that will just break things (actually this 
is what happened with 11/21)

I'm quite sorry if I did things wrong, it was my first attempt to sent 
patchset with tree-wide fixes. However, I don't see what I've done 
wrong... any hints on that will be appreciated.

Nikita

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-06-18 11:31 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 11:13 [PATCH 00/21] add and use devm_irq_of_parse_and_map() nyushchenko
2014-06-04 11:13 ` [PATCH 01/21] irq: add devres version of OF IRQ mapping routines nyushchenko
2014-06-04 13:39   ` Thomas Gleixner
2014-06-04 13:39     ` Thomas Gleixner
2014-06-04 11:13 ` [PATCH 02/21] ata: use devm_irq_of_parse_and_map() where appropriate nyushchenko
2014-06-04 11:13 ` [PATCH 03/21] exynos5440-cpufreq: use devm_irq_of_parse_and_map() nyushchenko
2014-06-04 11:13 ` [PATCH 04/21] omap-sham: " nyushchenko
2014-06-04 11:13 ` [PATCH 05/21] dma: use devm_irq_of_parse_and_map() where appropriate nyushchenko
2014-06-04 11:13 ` [PATCH 06/21] mpc85xx_edac: use devm_irq_of_parse_and_map() nyushchenko
2014-06-04 11:13 ` [PATCH 07/21] gpio: use devm_irq_of_parse_and_map() where appropriate nyushchenko
2014-06-04 11:13 ` [PATCH 08/21] i2c: " nyushchenko
2014-06-04 11:13 ` [PATCH 09/21] apbps2: use devm_irq_of_parse_and_map() nyushchenko
2014-06-04 11:13 ` [PATCH 10/21] media: use devm_irq_of_parse_and_map() where appropriate nyushchenko
2014-06-04 11:13 ` [PATCH 11/21] mfd: " nyushchenko
2014-06-04 11:13   ` nyushchenko-jFhMxQ4mL6a2X5qOxWx28w
2014-06-17 15:12   ` Lee Jones
2014-06-17 15:36     ` Nikita Yushchenko
2014-06-17 15:36       ` Nikita Yushchenko
2014-06-18  8:48       ` Lee Jones
2014-06-18 11:31         ` Nikita Yushchenko [this message]
2014-06-18 11:31           ` Nikita Yushchenko
2014-06-18 12:20           ` Lee Jones
2014-06-04 11:13 ` [PATCH 12/21] mpc5121_nfc: use devm_irq_of_parse_and_map() nyushchenko
2014-06-04 11:13 ` [PATCH 13/21] net/can: use devm_irq_of_parse_and_map() where appropriate nyushchenko
2014-06-04 11:13 ` [PATCH 14/21] net/ethernet: " nyushchenko
2014-06-04 11:13   ` nyushchenko-jFhMxQ4mL6a2X5qOxWx28w
2014-06-04 11:13 ` [PATCH 15/21] pinctrl: " nyushchenko
2014-06-04 11:13   ` nyushchenko-jFhMxQ4mL6a2X5qOxWx28w
2014-06-04 11:13 ` [PATCH 16/21] bq24190_charger: use devm_irq_of_parse_and_map() nyushchenko
2014-06-04 11:13 ` [PATCH 17/21] rtc-mpc5121: " nyushchenko
2014-06-04 11:13 ` [PATCH 18/21] spi: use devm_irq_of_parse_and_map() where appropriate nyushchenko
2014-06-04 11:13 ` [PATCH 19/21] exynos_tmu: use devm_irq_of_parse_and_map() nyushchenko
2014-06-04 11:13 ` [PATCH 20/21] usb: use devm_irq_of_parse_and_map() where appropriate nyushchenko
2014-06-04 11:13   ` nyushchenko-jFhMxQ4mL6a2X5qOxWx28w
2014-06-16  9:35   ` Andreas Larsson
2014-06-16  9:35     ` Andreas Larsson
2014-06-16  9:44     ` Nikita Yushchenko
2014-06-16  9:44       ` Nikita Yushchenko
2014-06-16  9:54       ` Andreas Larsson
2014-06-16  9:54         ` Andreas Larsson
2014-06-04 11:13 ` [PATCH 21/21] at91sam9_wdt: use devm_irq_of_parse_and_map() nyushchenko
2014-06-12 10:03 ` [PATCH 00/21] add and " Andreas Larsson
2014-06-12 10:03   ` Andreas Larsson
     [not found]   ` <5399AE1B.1080301@gaisler.com>
2014-06-12 19:02     ` Nikita Yushchenko
2014-06-12 19:02       ` Nikita Yushchenko
2014-06-16  8:23       ` Andreas Larsson
2014-06-16  8:23         ` Andreas Larsson
2014-06-16  8:36         ` Nikita Yushchenko
2014-06-16  8:36           ` Nikita Yushchenko
2014-06-16  8:36           ` Nikita Yushchenko
2014-06-16  9:29           ` Andreas Larsson
2014-06-16  9:29             ` Andreas Larsson

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=53A178AD.3060003@dev.rtsoft.ru \
    --to=nyushchenko@dev.rtsoft.ru \
    --cc=benh@kernel.crashing.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lugovskoy@dev.rtsoft.ru \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    /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.