All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Char/Misc driver fixes for 4.19-rc6
Date: Tue, 25 Sep 2018 17:56:39 +0200	[thread overview]
Message-ID: <20180925155639.GA8368@kroah.com> (raw)
In-Reply-To: <CAK8P3a2uRUerniKg7cZ+OuX8QLq+9f+SQKzXO9m6-Li6AYXJMA@mail.gmail.com>

On Tue, Sep 25, 2018 at 05:31:03PM +0200, Arnd Bergmann wrote:
> On Tue, Sep 25, 2018 at 4:54 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Sep 25, 2018 at 04:23:44PM +0200, Greg KH wrote:
> > > [Yes, the oddity of sending a pull request to myself is not lost on me...]
> >
> > And, I totally messed this up.  Ugh, what kind of idiot does something
> > like this!  It's not like I haven't been doing this for years!  I should
> > know better...
> 
> Ah, I was wondering about that. I even found the char-misc-4.19-rc6 tag,
> but it didn't add up. If you want the signoff chain to make more sense,
> you can add my
> 
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> 
> when you pull in your own tag. The resource handling in
> drivers/hwtracing/intel_th/core.c does look a bit odd, which
> confused me for a bit, but that was already the case before
> the patches.

Thanks for the review.  Yeah, that code is "odd" but then again, all of
the hwtracing code is strange :)

I've already pulled this tag into Linus's tree, I though I would be
passive-aggressive and not tell myself that it was done...

thanks,

greg "this is strange" k-h

      reply	other threads:[~2018-09-25 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 14:23 [GIT PULL] Char/Misc driver fixes for 4.19-rc6 Greg KH
2018-09-25 14:54 ` Greg KH
2018-09-25 15:31   ` Arnd Bergmann
2018-09-25 15:56     ` gregkh [this message]

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=20180925155639.GA8368@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.