All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Andra Paraschiv <andraprs@amazon.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Alexandru Ciobotaru <alcioa@amazon.com>,
	Kamal Mostafa <kamal@canonical.com>,
	Alexandru Vasile <lexnv@amazon.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stefano Garzarella <sgarzare@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>, kvm <kvm@vger.kernel.org>,
	ne-devel-upstream <ne-devel-upstream@amazon.com>
Subject: Re: [PATCH v1 3/3] nitro_enclaves: Add fixes for checkpatch and docs reports
Date: Fri, 27 Aug 2021 10:43:30 +0200	[thread overview]
Message-ID: <YSilspuLarIKRquD@kroah.com> (raw)
In-Reply-To: <20210826173451.93165-4-andraprs@amazon.com>

On Thu, Aug 26, 2021 at 08:34:51PM +0300, Andra Paraschiv wrote:
> Fix the reported issues from checkpatch and kernel-doc scripts.
> 
> Update the copyright statements to include 2021, where changes have been
> made over this year.
> 
> Signed-off-by: Andra Paraschiv <andraprs@amazon.com>

Please break this up into "one patch per logical change" do not mix
different things in the same commit.

thanks,

greg k-h

  parent reply	other threads:[~2021-08-27  8:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 17:34 [PATCH v1 0/3] nitro_enclaves: Add support for Arm64 Andra Paraschiv
2021-08-26 17:34 ` [PATCH v1 1/3] nitro_enclaves: Enable Arm support Andra Paraschiv
2021-08-27  7:06   ` Stefano Garzarella
2021-08-27  8:43   ` Greg KH
2021-08-27 10:19     ` Paraschiv, Andra-Irina
2021-08-26 17:34 ` [PATCH v1 2/3] nitro_enclaves: Update documentation for " Andra Paraschiv
2021-08-27  7:21   ` Stefano Garzarella
2021-08-27  9:35     ` Paraschiv, Andra-Irina
2021-08-26 17:34 ` [PATCH v1 3/3] nitro_enclaves: Add fixes for checkpatch and docs reports Andra Paraschiv
2021-08-26 17:51   ` Vitaly Kuznetsov
2021-08-26 18:22     ` Paraschiv, Andra-Irina
2021-08-27  8:43   ` Greg KH [this message]
2021-08-27 10:22     ` Paraschiv, Andra-Irina

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=YSilspuLarIKRquD@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alcioa@amazon.com \
    --cc=andraprs@amazon.com \
    --cc=kamal@canonical.com \
    --cc=kvm@vger.kernel.org \
    --cc=lexnv@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ne-devel-upstream@amazon.com \
    --cc=pbonzini@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vkuznets@redhat.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.