All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dwaipayan Ray <dwaipayanray1@gmail.com>
To: Joe Perches <joe@perches.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	linux-kernel-mentees@lists.linuxfoundation.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Patches from the future - can checkpatch help?
Date: Mon, 1 Feb 2021 22:04:01 +0530	[thread overview]
Message-ID: <CABJPP5AxB8-kafFEpsMydg8eMx8bH5ooT5g7r0fKWV2T2Hjtng@mail.gmail.com> (raw)

Hi,
on linux-next,
$ git log --pretty=format:"%h%x09%ad" | awk '$6>2021 {print $1}'
gives:
4a2d78822fdf
12ca45fea91c
09f2724a786f

These are patches from the year 2085, 2037 and 2030 respectively.

Would a checkpatch rule be helpful for these or are they too
isolated to waste runtime on?

Thanks!
Dwaipayan.

WARNING: multiple messages have this Message-ID (diff)
From: Dwaipayan Ray <dwaipayanray1@gmail.com>
To: Joe Perches <joe@perches.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	 linux-kernel-mentees@lists.linuxfoundation.org,
	 linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Linux-kernel-mentees] Patches from the future - can checkpatch help?
Date: Mon, 1 Feb 2021 22:04:01 +0530	[thread overview]
Message-ID: <CABJPP5AxB8-kafFEpsMydg8eMx8bH5ooT5g7r0fKWV2T2Hjtng@mail.gmail.com> (raw)

Hi,
on linux-next,
$ git log --pretty=format:"%h%x09%ad" | awk '$6>2021 {print $1}'
gives:
4a2d78822fdf
12ca45fea91c
09f2724a786f

These are patches from the year 2085, 2037 and 2030 respectively.

Would a checkpatch rule be helpful for these or are they too
isolated to waste runtime on?

Thanks!
Dwaipayan.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

             reply	other threads:[~2021-02-01 16:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 16:34 Dwaipayan Ray [this message]
2021-02-01 16:34 ` [Linux-kernel-mentees] Patches from the future - can checkpatch help? Dwaipayan Ray
2021-02-01 16:37 ` Greg KH
2021-02-01 16:37   ` Greg KH
2021-02-01 16:50   ` Lukas Bulwahn
2021-02-01 16:50     ` Lukas Bulwahn
2021-02-01 17:11     ` Dwaipayan Ray
2021-02-01 17:11       ` Dwaipayan Ray
2021-02-02 12:48       ` Joe Perches
2021-02-02 12:48         ` Joe Perches
2021-02-02 14:54         ` Philip Li
2021-02-02 14:54           ` Philip Li
2021-02-01 17:59     ` Theodore Ts'o
2021-02-01 17:59       ` Theodore Ts'o
2021-02-01 17:01   ` Dwaipayan Ray
2021-02-01 17:01     ` Dwaipayan Ray
2021-02-02 11:57     ` Greg KH
2021-02-02 11:57       ` Greg KH

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=CABJPP5AxB8-kafFEpsMydg8eMx8bH5ooT5g7r0fKWV2T2Hjtng@mail.gmail.com \
    --to=dwaipayanray1@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.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.