linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Bilbao <bilbao@vt.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Matthew Wilcox <willy@infradead.org>,
	Arnd Bergmann <arnd@arndb.de>, kbuild test robot <lkp@intel.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5] include: linux: Reorganize timekeeping and ktime headers
Date: Tue, 16 Nov 2021 17:11:07 -0500	[thread overview]
Message-ID: <ce75dfa1-b51d-1988-9371-ca90ab5e1535@vt.edu> (raw)
In-Reply-To: <YYN78YlFrV0vFPq9@kroah.com>

Hello again,

On 11/4/21 2:21 AM, Greg KH wrote:
> On Wed, Nov 03, 2021 at 03:33:52PM -0400, Carlos Bilbao wrote:
>> Hello everyone,
>>
>> Some time ago I sent a small patch to avoid implicit function declaration. 
>> In particular, timekeeping.h was using ktime_to_ns(), a static function defined 
>> in a header it does no include, ktime.h. Some maintainers saw this as an 
>> opportunity to reorganize ktime, and so I did and tested for all architectures.
>> Now, this patch has fallen into the "limbo of patches", so the original problem
>> remains unsolved. Please, either take a look at this or check the original
>> patch for the header dependencies.
> 
> Please just resend after 5.16-rc1 is out, there's nothing we can do with
> this at this point in time.
> 
> thanks,
> 
> greg k-h
> 

I think that now it is a good time to send :)

Thanks!

Carlos.

  reply	other threads:[~2021-11-16 22:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 19:30 arch/powerpc/kernel/time.c:801:5: error: no previous prototype for 'update_persistent_clock64' kernel test robot
2021-08-01 20:12 ` [PATCH v4.1] include: linux: Reorganize timekeeping and ktime headers Carlos Bilbao
2021-08-09 15:07   ` Geert Uytterhoeven
2021-08-09 16:39     ` Carlos Bilbao
2021-08-22 13:15       ` Carlos Bilbao
2021-08-22 13:23         ` Greg KH
2021-08-22 13:27           ` [PATCH v5] " Carlos Bilbao
2021-09-12 15:33             ` Carlos Bilbao
2021-11-03 19:33               ` Carlos Bilbao
2021-11-04  6:21                 ` Greg KH
2021-11-16 22:11                   ` Carlos Bilbao [this message]
2021-11-16 22:11                     ` Carlos Bilbao
2021-12-01 15:22                       ` Carlos Bilbao
2021-12-03 13:28                         ` 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=ce75dfa1-b51d-1988-9371-ca90ab5e1535@vt.edu \
    --to=bilbao@vt.edu \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=tglx@linutronix.de \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).