All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Rob Herring <robh@kernel.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Kevin Hilman <khilman@baylibre.com>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	Carlo Caione <carlo@caione.org>,
	linux-amlogic@lists.infradead.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] i2c: meson: add gxbb compatible string
Date: Sat, 24 Sep 2016 01:26:42 +0200	[thread overview]
Message-ID: <20160923232641.GB5683@katana> (raw)
In-Reply-To: <CAL_JsqKi9Dk5-nF9xFD-89TTUinaGjMv5s1=N2b-Xyu98b+S3w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]


> > I intentionally don't ask people to send me the patches squashed. So,
> > you will have them seperate in patchwork et al. I only squash them just
> > before commiting to my tree. That's because I found that when digging
> > through git history, it is much more convenient to have all the
> > information in one commit.
> 
> If git history was the only thing that mattered, then that would be
> fine. But it is not. Maintainers should apply what's on the list.
> Period.

Huh? If you would *ask* me to stop squashing, I am listening to reasons.
If you want to force arbitrary rules on me, I am not. There are reasons
where squashing/modifying patches makes more sense compared to forcing
the author to resend. DTS bindings may not be one, we can discuss that.
But that rule without allowing exceptions seems impractical to me.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] i2c: meson: add gxbb compatible string
Date: Sat, 24 Sep 2016 01:26:42 +0200	[thread overview]
Message-ID: <20160923232641.GB5683@katana> (raw)
In-Reply-To: <CAL_JsqKi9Dk5-nF9xFD-89TTUinaGjMv5s1=N2b-Xyu98b+S3w@mail.gmail.com>


> > I intentionally don't ask people to send me the patches squashed. So,
> > you will have them seperate in patchwork et al. I only squash them just
> > before commiting to my tree. That's because I found that when digging
> > through git history, it is much more convenient to have all the
> > information in one commit.
> 
> If git history was the only thing that mattered, then that would be
> fine. But it is not. Maintainers should apply what's on the list.
> Period.

Huh? If you would *ask* me to stop squashing, I am listening to reasons.
If you want to force arbitrary rules on me, I am not. There are reasons
where squashing/modifying patches makes more sense compared to forcing
the author to resend. DTS bindings may not be one, we can discuss that.
But that rule without allowing exceptions seems impractical to me.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160924/8e01fc6e/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/2] i2c: meson: add gxbb compatible string
Date: Sat, 24 Sep 2016 01:26:42 +0200	[thread overview]
Message-ID: <20160923232641.GB5683@katana> (raw)
In-Reply-To: <CAL_JsqKi9Dk5-nF9xFD-89TTUinaGjMv5s1=N2b-Xyu98b+S3w@mail.gmail.com>


> > I intentionally don't ask people to send me the patches squashed. So,
> > you will have them seperate in patchwork et al. I only squash them just
> > before commiting to my tree. That's because I found that when digging
> > through git history, it is much more convenient to have all the
> > information in one commit.
> 
> If git history was the only thing that mattered, then that would be
> fine. But it is not. Maintainers should apply what's on the list.
> Period.

Huh? If you would *ask* me to stop squashing, I am listening to reasons.
If you want to force arbitrary rules on me, I am not. There are reasons
where squashing/modifying patches makes more sense compared to forcing
the author to resend. DTS bindings may not be one, we can discuss that.
But that rule without allowing exceptions seems impractical to me.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20160924/8e01fc6e/attachment.sig>

  reply	other threads:[~2016-09-23 23:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  9:49 [PATCH 0/2] i2c: meson: add gxbb compatible string Jerome Brunet
2016-09-14  9:49 ` Jerome Brunet
2016-09-14  9:49 ` Jerome Brunet
2016-09-14  9:49 ` [PATCH 1/2] " Jerome Brunet
2016-09-14  9:49   ` Jerome Brunet
2016-09-14  9:49   ` Jerome Brunet
2016-09-14 15:19   ` Kevin Hilman
2016-09-14 15:19     ` Kevin Hilman
2016-09-14 15:19     ` Kevin Hilman
     [not found] ` <1473846557-18123-1-git-send-email-jbrunet-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-09-14  9:49   ` [PATCH 2/2] dt-bindings: i2c-meson: " Jerome Brunet
2016-09-14  9:49     ` Jerome Brunet
2016-09-14  9:49     ` Jerome Brunet
     [not found]     ` <1473846557-18123-3-git-send-email-jbrunet-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-09-14 15:19       ` Kevin Hilman
2016-09-14 15:19         ` Kevin Hilman
2016-09-14 15:19         ` Kevin Hilman
2016-09-15 19:41 ` [PATCH 0/2] i2c: meson: " Wolfram Sang
2016-09-15 19:41   ` Wolfram Sang
2016-09-15 19:41   ` Wolfram Sang
2016-09-23 15:01   ` Rob Herring
2016-09-23 15:01     ` Rob Herring
2016-09-23 15:01     ` Rob Herring
2016-09-23 22:13     ` Wolfram Sang
2016-09-23 22:13       ` Wolfram Sang
2016-09-23 22:13       ` Wolfram Sang
2016-09-23 23:04       ` Rob Herring
2016-09-23 23:04         ` Rob Herring
2016-09-23 23:04         ` Rob Herring
2016-09-23 23:26         ` Wolfram Sang [this message]
2016-09-23 23:26           ` Wolfram Sang
2016-09-23 23:26           ` Wolfram Sang
2016-09-24  1:02           ` Rob Herring
2016-09-24  1:02             ` Rob Herring
2016-09-24  1:02             ` Rob Herring
2016-09-24  8:41             ` Wolfram Sang
2016-09-24  8:41               ` Wolfram Sang
2016-09-24  8:41               ` Wolfram Sang

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=20160923232641.GB5683@katana \
    --to=wsa@the-dreams.de \
    --cc=carlo@caione.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=robh@kernel.org \
    /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.