All of lore.kernel.org
 help / color / mirror / Atom feed
From: mark gross <mgross@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] copyright owner and author clean up for intel iommu and related files
Date: Mon, 25 Feb 2008 07:50:14 -0800	[thread overview]
Message-ID: <20080225155014.GA22018@linux.intel.com> (raw)
In-Reply-To: <20080223112022.8e4fdde2.akpm@linux-foundation.org>

On Sat, Feb 23, 2008 at 11:20:22AM -0800, Andrew Morton wrote:
> On Sat, 23 Feb 2008 11:06:49 -0800 Greg KH <greg@kroah.com> wrote:
> 
> > On Sat, Feb 23, 2008 at 12:04:43AM -0800, Andrew Morton wrote:
> > > On Thu, 21 Feb 2008 10:15:55 -0800 mark gross <mgross@linux.intel.com> wrote:
> > > 
> > > > Index: linux-2.6.24-mm1/drivers/pci/dmar.c
> > > 
> > > I guess this is strictly a greg-pci-tree thing.  Greg, how do you want
> > > to play intel-iommu?
> > 
> > Yes, I'll take those.  I'm pretty sure I even have the hardware here to
> > test that the code doesn't crash :)
> > 
> 
> ok..
> 
> I have another one queued for 2.6.26-via-greg:
> pci-iova-rb-tree-setup-tweak.patch
> 

Should I start sending all the intel-iommu related stuff to Greg then?

--mgross

> And one queued for 2.6.25: iova-lockdep-false-alarm-fix.patch which
> according to my current processes will be sent to you after I've tested it
> a bit with "for 2.6.25?" in its Subject:
> 
> My list of for-2.6.25-after-a-bit-of-testing patches is large:
> 
> 
> rtc-cmos-display-hpet-emulation-mode.patch
> register_memory-unregister_memory-fix-use-after-free-and-refcounting.patch
> acer-wmi-fail-gracefully-if-acpi-is-disabled.patch
> tc1100-wmi-fail-gracefully-if-acpi-is-disabled.patch
> dmi-dont-save-the-same-device-twice-was-smbios-dmi-add-type-41-=-onboard-devices-extended-information.patch
> uml-remove-unused-sigcontext-accessors.patch
> uml-fix-helper_wait-calls-in-watchdog.patch
> uml-fix-fp-register-corruption.patch
> x86-cast-cmpxchg-and-cmpxchg_local-result-for-386-and-486.patch
> nbd-make-nbd-default-to-deadline-i-o-scheduler.patch
> efs-move-headers-out-of-include-linux.patch
> percpu-fix-debug_preempt-per_cpu-checking.patch
> proc-add-rlimit_rttime-to-proc-pid-limits.patch
> drivers-video-uvesafbc-fix-section-mismatch-warning-in-param_set_scroll.patch
> dmi-prevent-linked-list-corruption-resent.patch
> x86-fix-clearcopy_user_page-declarations-in-pageh.patch
> futex-fix-init-order.patch
> futex-runtime-enable-pi-and-robust-functionality.patch
> h8300-signalc-typo-fix.patch
> h8300-uaccessh-update.patch
> h8300-irq-handling-update.patch
> h8300-defconfig-update.patch
> kernel-doc-fix-function-pointer-parameter-parsing.patch
> mpt-fusion-dont-oops-if-numphys==0.patch
> bluetooth-hci_core-defer-hci_unregister_sysfs.patch
> e100-do-suspend-shutdown-like-e1000.patch
> dm-raid1-bitops-bug.patch
> alloc_percpu-fails-to-allocate-percpu-data.patch
> scsi-qla4xxx-ql4_isrc-unchangelogged-patch.patch
> iova-lockdep-false-alarm-fix.patch
> cgroup-memory-controller-document-huge-memory-cache-overhead-in-kconfig.patch
> kprobes-refuse-kprobe-insertion-on-add-sub_preempt_counter.patch
> sh-revert-dreamcast-pci-change.patch
> bluetooth-conwise-technology-based-adapters-with-buggy-sco-support-bugzilla-9027.patch
> pm-remove-unbalanced-mutex_unlock-from-dpm_resume.patch
> message-fusion-mptbasec-fix-use-after-frees.patch
> ieee80211-fix-broken-error-handling-in-ieee80211_sta_process_addba_request.patch
> smack-update-for-file-capabilities.patch
> fix-typo-in-tick-broadcastc.patch
> dm-raid1c-fix-null-dereferences.patch
> usb-queue-usb-usb_cdc_get_encapsulated_response-message.patch
> i8042-use-sgi_has_i8042-to-select-sgi-i8042-handlinig.patch
> solve-section-mismatch-for-free_area_init_core.patch
> #
> cgroup-fix-and-update-documentation.patch
> cgroup-fix-comments.patch
> cgroup-clean-up-cgrouph.patch
> cgroup-fix-memory-leak-in-cgroup_get_sb.patch
> cgroup-fix-subsys-bitops.patch
> cgroup-remove-duplicate-code-in-find_css_set.patch
> cgroup-remove-dead-code-in-cgroup_get_rootdir.patch
> #
> memcgroup-fix-and-update-documentation.patch
> memcgroup-remove-a-useless-vm_bug_on.patch
> memcgroup-return-negative-error-code-in-mem_cgroup_create.patch
> #
> #kernel-irq-chipc-irq-disable-shutdown-bug.patch: needs acks
> kernel-irq-chipc-irq-disable-shutdown-bug.patch
> #
> #revert-sh-use-ctrl_in-out-for-on-chip-pci-access.patch: being worked on
> #revert-sh-use-ctrl_in-out-for-on-chip-pci-access.patch
> #
> kthread-synchronization-issues.patch
> #kthread-add-a-missing-memory-barrier-to-kthread_stop.patch: nop, do it in wake_up
> kthread-add-a-missing-memory-barrier-to-kthread_stop.patch
> kthread-call-wake_up_process-without-the-lock-being-held.patch
> fix-b43-driver-build-for-arm.patch
> vt-notifier-fix-for-vt-switch.patch
> 

  reply	other threads:[~2008-02-25 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 18:15 [PATCH] copyright owner and author clean up for intel iommu and related files mark gross
2008-02-23  8:04 ` Andrew Morton
2008-02-23 19:06   ` Greg KH
2008-02-23 19:20     ` Andrew Morton
2008-02-25 15:50       ` mark gross [this message]
2008-02-25 17:54         ` Greg KH
2008-02-25 18:28           ` Andrew Morton
2008-02-26  0:45             ` mark gross

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=20080225155014.GA22018@linux.intel.com \
    --to=mgross@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.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.