All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	"open list:AMD IOMMU (AMD-VI)" <iommu@lists.linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] dma-mapping file renames for Linux 4.18
Date: Wed, 20 Jun 2018 07:52:53 +0900	[thread overview]
Message-ID: <CA+55aFwEZHzxXDdUGwwuw5HYZB9R5CfTv3XKbft46+ai7C_Q7w@mail.gmail.com> (raw)
In-Reply-To: <20180619044358.snyej666melspv46@infradead.org>

On Tue, Jun 19, 2018 at 1:44 PM Christoph Hellwig <hch@infradead.org> wrote:
>
> below is a rename of the assorted dma-mapping files to that they live
> under kernel/dma and lose their dma-* prefixes.  If there is any time
> to do this it is right after -rc1, so let me know if this is something
> you'd take.

I iwas going to take it, but then I noticed that it's an unsigned tag
from a random site.

Yeah, yeah, I have pulled such things in the past, but  I'm really
trying to convince people to use signed tags.

I prefer signed tags even on kernel.org, where I know the security is
tight. On other sites, I really want that warm fuzzy feeling of
knowing that yeah, you actually put that code there.

             Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: "open list:AMD IOMMU (AMD-VI)"
	<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Konrad Rzeszutek Wilk
	<konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Subject: Re: [GIT PULL] dma-mapping file renames for Linux 4.18
Date: Wed, 20 Jun 2018 07:52:53 +0900	[thread overview]
Message-ID: <CA+55aFwEZHzxXDdUGwwuw5HYZB9R5CfTv3XKbft46+ai7C_Q7w@mail.gmail.com> (raw)
In-Reply-To: <20180619044358.snyej666melspv46-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

On Tue, Jun 19, 2018 at 1:44 PM Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> wrote:
>
> below is a rename of the assorted dma-mapping files to that they live
> under kernel/dma and lose their dma-* prefixes.  If there is any time
> to do this it is right after -rc1, so let me know if this is something
> you'd take.

I iwas going to take it, but then I noticed that it's an unsigned tag
from a random site.

Yeah, yeah, I have pulled such things in the past, but  I'm really
trying to convince people to use signed tags.

I prefer signed tags even on kernel.org, where I know the security is
tight. On other sites, I really want that warm fuzzy feeling of
knowing that yeah, you actually put that code there.

             Linus

  reply	other threads:[~2018-06-19 22:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  4:43 [GIT PULL] dma-mapping file renames for Linux 4.18 Christoph Hellwig
2018-06-19  4:43 ` Christoph Hellwig
2018-06-19 22:52 ` Linus Torvalds [this message]
2018-06-19 22:52   ` Linus Torvalds
2018-06-20  4:34   ` Christoph Hellwig
2018-06-20  4:34     ` Christoph Hellwig

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=CA+55aFwEZHzxXDdUGwwuw5HYZB9R5CfTv3XKbft46+ai7C_Q7w@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.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.