Re: message ids

Re: message ids

[Rob Landley]

On 11/12/20 1:47 AM, Rob Landley wrote:
> Message-Id: <20200917154547.139019-1-fazilyildiran@gmail.com>
> Message-ID: <93d98bab-01dd-5530-9fdb-76faf8dcdd41@infradead.org>
> Message-ID: <20200919025206.17729-1-miaoqinglang@huawei.com>
> Message-Id: <20200924043139.522028-1-hch@lst.de> # does not apply with git am???
> Message-Id: <1602474624-3225-1-git-send-email-hejinyang@loongson.cn>
> Message-Id: <20201012154050.68039-1-andriy.shevchenko@linux.intel.com>
> Message-Id: <1604889952-30841-1-git-send-email-wangqing@vivo.com>
> Message-Id: <1604889303-26722-1-git-send-email-wangqing@vivo.com>
> Message-ID: <66582445-4ec9-86d0-e286-8e21590f608a@kernel.dk>
> Message-Id: <20201110154939.3285928-1-geert+renesas@glider.be>
> Message-Id: <20201110155029.3286090-1-geert+renesas@glider.be>
> 
> I have no idea why the hch@lst.de one applies with "patch -p1" but not with
> "git am", that's where I ran out of brain. But they all apply as patches and the
> result boots.

FYI here are the patches from this list I forwarded to Rich right after -rc3
came out. They built in my local tree, the result booted, and I didn't spot
obvious regressions.

If anybody else wants to try them, I can put them in a -git tree or attach them
to an email?

Rob

Re: message ids

[Geert Uytterhoeven]

Hi Rob,

On Sun, Nov 22, 2020 at 4:00 PM Rob Landley <rob@landley.net> wrote:
> On 11/12/20 1:47 AM, Rob Landley wrote:
> > Message-Id: <20200917154547.139019-1-fazilyildiran@gmail.com>
> > Message-ID: <93d98bab-01dd-5530-9fdb-76faf8dcdd41@infradead.org>
> > Message-ID: <20200919025206.17729-1-miaoqinglang@huawei.com>
> > Message-Id: <20200924043139.522028-1-hch@lst.de> # does not apply with git am???
> > Message-Id: <1602474624-3225-1-git-send-email-hejinyang@loongson.cn>
> > Message-Id: <20201012154050.68039-1-andriy.shevchenko@linux.intel.com>
> > Message-Id: <1604889952-30841-1-git-send-email-wangqing@vivo.com>
> > Message-Id: <1604889303-26722-1-git-send-email-wangqing@vivo.com>
> > Message-ID: <66582445-4ec9-86d0-e286-8e21590f608a@kernel.dk>
> > Message-Id: <20201110154939.3285928-1-geert+renesas@glider.be>
> > Message-Id: <20201110155029.3286090-1-geert+renesas@glider.be>
> >
> > I have no idea why the hch@lst.de one applies with "patch -p1" but not with
> > "git am", that's where I ran out of brain. But they all apply as patches and the
> > result boots.
>
> FYI here are the patches from this list I forwarded to Rich right after -rc3
> came out. They built in my local tree, the result booted, and I didn't spot
> obvious regressions.
>
> If anybody else wants to try them, I can put them in a -git tree or attach them
> to an email?

BTW, the modern way to refer to patches is by prepending
"https://lore.kernel.org/r/"
to the message IDs.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Re: message ids

[Rob Landley]

On 11/23/20 2:11 AM, Geert Uytterhoeven wrote:
> Hi Rob,
> 
> On Sun, Nov 22, 2020 at 4:00 PM Rob Landley <rob@landley.net> wrote:
>> On 11/12/20 1:47 AM, Rob Landley wrote:
>>> Message-Id: <20200917154547.139019-1-fazilyildiran@gmail.com>
>>> Message-ID: <93d98bab-01dd-5530-9fdb-76faf8dcdd41@infradead.org>
>>> Message-ID: <20200919025206.17729-1-miaoqinglang@huawei.com>
>>> Message-Id: <20200924043139.522028-1-hch@lst.de> # does not apply with git am???
>>> Message-Id: <1602474624-3225-1-git-send-email-hejinyang@loongson.cn>
>>> Message-Id: <20201012154050.68039-1-andriy.shevchenko@linux.intel.com>
>>> Message-Id: <1604889952-30841-1-git-send-email-wangqing@vivo.com>
>>> Message-Id: <1604889303-26722-1-git-send-email-wangqing@vivo.com>
>>> Message-ID: <66582445-4ec9-86d0-e286-8e21590f608a@kernel.dk>
>>> Message-Id: <20201110154939.3285928-1-geert+renesas@glider.be>
>>> Message-Id: <20201110155029.3286090-1-geert+renesas@glider.be>
>>>
>>> I have no idea why the hch@lst.de one applies with "patch -p1" but not with
>>> "git am", that's where I ran out of brain. But they all apply as patches and the
>>> result boots.
>>
>> FYI here are the patches from this list I forwarded to Rich right after -rc3
>> came out. They built in my local tree, the result booted, and I didn't spot
>> obvious regressions.
>>
>> If anybody else wants to try them, I can put them in a -git tree or attach them
>> to an email?
> 
> BTW, the modern way to refer to patches is by prepending
> "https://lore.kernel.org/r/"
> to the message IDs.

That was a grep of the saved email files because Rich asked for msgids, and then
I forwarded the email here after 2 weeks later after repeated poking didn't get
further action on the pending patch pile.

I just did a fresh pull and git log arch/sh/boards/mach-sh03/rtc.c and the last
time it was touched is January, despite

  Message-Id: <1604889303-26722-1-git-send-email-wangqing@vivo.com>

Touching that file. (And that's an obvious "remove duplicate #include" not "I
decided not to apply this one because $TECHNICAL_REASON".)

The pull I did was to a tree with all the patches applied and it didn't complain
about conflicts, so presumably they still apply?

Rob