All of lore.kernel.org
 help / color / mirror / Atom feed
From: nobuhiro1.iwamatsu@toshiba.co.jp (nobuhiro1.iwamatsu at toshiba.co.jp)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH resend] arm64: dts: Remove inconsistent use of 'arm, armv8' compatible string
Date: Thu, 5 Sep 2019 01:16:55 +0000	[thread overview]
Message-ID: <OSAPR01MB32343F977759B44B739099C892BB0@OSAPR01MB3234.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <1137cd6d-4a85-8d19-a390-4aa539b8034f@siemens.com>

https://patchwork.kernel.org/patch/10754905/

> -----Original Message-----
> From: Jan Kiszka [mailto:jan.kiszka at siemens.com]
> Sent: Tuesday, September 3, 2019 10:56 PM
> To: iwamatsu nobuhiro(?? ?? ????????)
> <nobuhiro1.iwamatsu@toshiba.co.jp>; fabrizio.castro at bp.renesas.com;
> pavel at denx.de
> Cc: cip-dev at lists.cip-project.org; biju.das at bp.renesas.com
> Subject: Re: [cip-dev] [PATCH resend] arm64: dts: Remove inconsistent
> use of 'arm, armv8' compatible string
> 
> On 03.09.19 06:45, nobuhiro1.iwamatsu at toshiba.co.jp wrote:
> > Hi Fabrizio,
> >
> > Thanks for your test.
> >
> >> -----Original Message-----
> >> From: Fabrizio Castro [mailto:fabrizio.castro at bp.renesas.com]
> >> Sent: Monday, September 2, 2019 6:05 PM
> >> To: Pavel Machek <pavel@denx.de>
> >> Cc: Chris Paterson <Chris.Paterson2@renesas.com>; Biju Das
> >> <biju.das@bp.renesas.com>; iwamatsu nobuhiro(?? ?? ?????
> ??
> >> ?) <nobuhiro1.iwamatsu@toshiba.co.jp>;
> cip-dev at lists.cip-project.org
> >> Subject: RE: [PATCH resend] arm64: dts: Remove inconsistent use of
> >> 'arm,armv8' compatible string
> >>
> >> Hi Pavel,
> >>
> >> Thank you for the feedback!
> >>
> >>> From: Pavel Machek <pavel@denx.de>
> >>> Sent: 02 September 2019 10:01
> >>> Subject: Re: [PATCH resend] arm64: dts: Remove inconsistent use of
> >>> 'arm,armv8' compatible string
> >>>
> >>> On Mon 2019-09-02 08:51:12, Fabrizio Castro wrote:
> >>>> Hi Pavel,
> >>>>
> >>>> I have put you in CC (and kept the ML as recipient this time
> >>>> around), did you receive the patch with or without the space?
> >>>
> >>> I got just one copy of email, and it does not have [cip-dev]
> >>> marking, so I assume it is the direct one.
> >>>
> >>> No extra space.
> >>
> >> Then it's down to the mailing list, somehow, this same email reached
> >> the ML, with a space...
> >>
> https://lists.cip-project.org/pipermail/cip-dev/2019-September/00315
> >> 8.html
> >> https://patchwork.kernel.org/patch/11126171/
> >>
> >
> > Hmmm. There may be a problem in Mailman.
> >
> 
> Comparing the original patch
> (https://lore.kernel.org/linux-amlogic/20190109202934.29304-1-robh at k
> ernel.org/raw) to ours:
> 
> X-Mailman-Version: 2.1.21 (looks fine)
> X-Mailman-Version: 2.1.12 (our potentially broken version)
> 
> It looks like 2.1.21 is starting the wrapped around subject line only
> with a single space while our version gained a tab. The latter is likely
> the core if the issue. I would not expect this difference to be a
> configuration option of mailman, rather an issue in the older version
> 

Thank you for information.

And the original patch thread is interesting.
Each subject has space issues. Please see "Thread overview" at the bottom of the page.
  https://lore.kernel.org/linux-amlogic/2053cd60-479a-4219-2415-ebb6a860a8e7 at kernel.org/t/


> HTH,
> Jan
> 

Best regards,
  Nobuhiro

  reply	other threads:[~2019-09-05  1:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  8:48 [cip-dev] [PATCH resend] arm64: dts: Remove inconsistent use of 'arm, armv8' compatible string Fabrizio Castro
2019-09-02  8:51 ` Fabrizio Castro
2019-09-02  9:00   ` Pavel Machek
2019-09-02  9:05     ` Fabrizio Castro
2019-09-03  4:45       ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-09-03 13:56         ` Jan Kiszka
2019-09-05  1:16           ` nobuhiro1.iwamatsu at toshiba.co.jp [this message]
2019-09-05  7:27             ` Jan Kiszka

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=OSAPR01MB32343F977759B44B739099C892BB0@OSAPR01MB3234.jpnprd01.prod.outlook.com \
    --to=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.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.