All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander A. Klimov" <grandmaster@al2klimov.de>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	santosh.shilimkar@oracle.com, davem@davemloft.net,
	kuba@kernel.org, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for v5.9] RDS: Replace HTTP links with HTTPS ones
Date: Tue, 21 Jul 2020 08:43:00 +0200	[thread overview]
Message-ID: <f1df7901-35ef-af8a-b852-e5e89ababf01@al2klimov.de> (raw)
In-Reply-To: <20200721060529.GF1080481@unreal>



Am 21.07.20 um 08:05 schrieb Leon Romanovsky:
> On Mon, Jul 20, 2020 at 11:34:00PM +0200, Alexander A. Klimov wrote:
>>
>>
>> Am 20.07.20 um 18:48 schrieb Leon Romanovsky:
>>> On Mon, Jul 20, 2020 at 08:36:35AM -0600, Jonathan Corbet wrote:
>>>> On Mon, 20 Jul 2020 17:07:16 +0300
>>>> Leon Romanovsky <leon@kernel.org> wrote:
>>>>
>>>>>> Do *you* want to review that megapatch?  The number of issues that have
>> This question is... interesting.
>> And no, I would not.
> 
> You are EXPECTED to review your work prior sending to the mailing list.
I meant I wouldn't review *one big* patch.
I didn't mean my actually sent smaller ones.

> 
>>
>>>>>> come up make it clear that these patches do, indeed, need review...
>>>>>
>>>>> Can you point me to the issues?
>>>>> What can go wrong with such a simple replacement?
>>>>
>>>> Some bits of the conversation:
>>>>
>>>>     https://lore.kernel.org/lkml/20200626110219.7ae21265@lwn.net/
>>>>     https://lore.kernel.org/lkml/20200626110706.7b5d4a38@lwn.net/
>>>>     https://lore.kernel.org/lkml/20200705142506.1f26a7e0@lwn.net/
>>>>     https://lore.kernel.org/lkml/20200713114321.783f0ae6@lwn.net/
>>>>     https://lore.kernel.org/lkml/202007081531.085533FC5@keescook/
>>>>
>>>> etc.
>>>
>>> After reading your links and especially this one.
>>> https://lore.kernel.org/lkml/20200713114321.783f0ae6@lwn.net/
>>> I don't understand why are we still seeing these patches?
>>>
>>> I gave to the author comments too, which were ignored.
>>> https://patchwork.kernel.org/patch/11644683/#23466547
>> I've added SPDXing (the automated way of course ;) ) to my todo list.
> 
> OMG, why don't you listen? We don't want your automatic patches.
Wrong.
*Some of you* don't want my automatic patches.
And *some others* already applied them and said thanks.

> 
> Thanks
> 
>>
>>>
>>> Thanks
>>>
>>>>
>>>> jon

  reply	other threads:[~2020-07-21  6:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 15:58 [PATCH for v5.9] RDS: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-20  4:56 ` Leon Romanovsky
2020-07-20 13:58   ` Jonathan Corbet
2020-07-20 14:07     ` Leon Romanovsky
2020-07-20 14:36       ` Jonathan Corbet
2020-07-20 16:48         ` Leon Romanovsky
2020-07-20 21:34           ` Alexander A. Klimov
2020-07-21  6:05             ` Leon Romanovsky
2020-07-21  6:43               ` Alexander A. Klimov [this message]
2020-07-21  8:54                 ` Leon Romanovsky

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=f1df7901-35ef-af8a-b852-e5e89ababf01@al2klimov.de \
    --to=grandmaster@al2klimov.de \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rds-devel@oss.oracle.com \
    --cc=santosh.shilimkar@oracle.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.