From: <gregkh@linuxfoundation.org>
To: gregkh@linuxfoundation.org, arnd@arndb.de
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "scsi: advansys.c: remove DMA build warning message" has been added to the 3.18-stable tree
Date: Thu, 04 May 2017 16:07:58 -0700 [thread overview]
Message-ID: <14939392781674@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
scsi: advansys.c: remove DMA build warning message
to the 3.18-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
scsi-advansys.c-remove-dma-build-warning-message.patch
and it can be found in the queue-3.18 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From foo@baz Thu May 4 16:05:52 PDT 2017
Date: Thu, 04 May 2017 16:05:52 -0700
To: Greg KH <gregkh@linuxfoundation.org>
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: scsi: advansys.c: remove DMA build warning message
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
The driver was finally converted to the "new" DMA api in newer kernels,
but here in 3.18, it never will happen, so just shut the warning up for
now as obviously no one is going to do anything about it.
Cc: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/scsi/advansys.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/scsi/advansys.c
+++ b/drivers/scsi/advansys.c
@@ -68,7 +68,7 @@
* 7. advansys_info is not safe against multiple simultaneous callers
* 8. Add module_param to override ISA/VLB ioport array
*/
-#warning this driver is still not properly converted to the DMA API
+/*#warning this driver is still not properly converted to the DMA API */
/* Enable driver /proc statistics. */
#define ADVANSYS_STATS
Patches currently in stable-queue which might be from gregkh@linuxfoundation.org are
queue-3.18/ib-iser-fix-sparse-warnings.patch
queue-3.18/cred-userns-define-current_user_ns-as-a-function.patch
queue-3.18/mips-kgdb-use-kernel-context-for-sleeping-threads.patch
queue-3.18/l2tp-fix-racy-sock_zapped-flag-check-in-l2tp_ip-6-_bind.patch
queue-3.18/mips-elf2ecoff-ignore-pt_mips_abiflags-program-headers.patch
queue-3.18/l2tp-purge-socket-queues-in-the-.destruct-callback.patch
queue-3.18/nfsd-check-for-oversized-nfsv2-v3-arguments.patch
queue-3.18/pci-xilinx-fix-harmless-format-string-warning.patch
queue-3.18/arm64-build-vdso-without-libgcov.patch
queue-3.18/handle-mismatched-open-calls.patch
queue-3.18/sparc64-kern_addr_valid-regression.patch
queue-3.18/arm64-provide-a-namespace-to-ncaps.patch
queue-3.18/alsa-ppc-awacs-shut-up-maybe-uninitialized-warning.patch
queue-3.18/sparc64-fix-kernel-panic-due-to-erroneous-ifdef-surrounding-pmd_write.patch
queue-3.18/mips-jz4740-fix-build-error-in-irq.h.patch
queue-3.18/net-tg3-avoid-uninitialized-variable-warning.patch
queue-3.18/sctp-listen-on-the-sock-only-when-it-s-state-is-listening-or-closed.patch
queue-3.18/ftrace-x86-fix-triple-fault-with-graph-tracing-and-suspend-to-ram.patch
queue-3.18/tty-isicom-fix-big-endian-compile-warning.patch
queue-3.18/mtd-avoid-stack-overflow-in-mtd-cfi-code.patch
queue-3.18/ib-qib-rename-bits_per_page-to-rvt_bits_per_page.patch
queue-3.18/posix_acl-clear-sgid-bit-when-setting-file-permissions.patch
queue-3.18/scsi-advansys.c-remove-dma-build-warning-message.patch
queue-3.18/ips-remove-pointless-warning.patch
queue-3.18/powerpc-ptrace-fix-out-of-bounds-array-access-warning.patch
queue-3.18/usb-gadget-f_midi-fixed-a-bug-when-buflen-was-smaller-than-wmaxpacketsize.patch
queue-3.18/input-i8042-add-clevo-p650rs-to-the-i8042-reset-list.patch
queue-3.18/xen-x86-don-t-lose-event-interrupts.patch
queue-3.18/alsa-seq-don-t-break-snd_use_lock_sync-loop-by-timeout.patch
queue-3.18/timerfd-protect-the-might-cancel-mechanism-proper.patch
queue-3.18/mm-avoid-setting-up-anonymous-pages-into-file-mapping.patch
queue-3.18/net-phy-handle-state-correctly-in-phy_stop_machine.patch
queue-3.18/staging-imx-drm-fix-indentation-warning.patch
queue-3.18/mlx5-avoid-build-warnings-on-32-bit.patch
queue-3.18/f2fs-do-more-integrity-verification-for-superblock.patch
queue-3.18/mm-cma-silence-warnings-due-to-max-usage.patch
queue-3.18/net-packet-fix-overflow-in-check-for-tp_frame_nr.patch
queue-3.18/misdn-avoid-arch-specific-__builtin_return_address-call.patch
queue-3.18/staging-bcm-add-32-bit-host-dependency.patch
queue-3.18/net-packet-fix-overflow-in-check-for-tp_reserve.patch
queue-3.18/netpoll-check-for-skb-queue_mapping.patch
queue-3.18/net-neigh-guard-against-null-solicit-method.patch
queue-3.18/staging-unisys-fix-build-warning-in-periodic_work.patch
queue-3.18/perf-tighten-and-fix-the-grouping-condition.patch
queue-3.18/p9_client_readdir-fix.patch
queue-3.18/message-i2o-fix-64bit-build-warnings.patch
queue-3.18/rds-fix-the-atomicity-for-congestion-map-update.patch
queue-3.18/staging-vt6655-fix-overly-large-stack-usage.patch
queue-3.18/mips-fix-crash-registers-on-non-crashing-cpus.patch
queue-3.18/alsa-pcm-call-kill_fasync-in-stream-lock.patch
queue-3.18/drbd-avoid-redefinition-of-bits_per_page.patch
queue-3.18/xc2028-unlock-on-error-in-xc2028_set_config.patch
queue-3.18/infiniband-mlx5-avoid-a-compile-time-warning.patch
queue-3.18/ip6mr-fix-notification-device-destruction.patch
queue-3.18/arm-cns3xxx-shut-up-frame-size-warning.patch
queue-3.18/ext4-check-if-in-inode-xattr-is-corrupted-in-ext4_expand_extra_isize_ea.patch
queue-3.18/regulator-core-fix-regualtor_ena_gpio_free-not-to-access-pin-after-freeing.patch
queue-3.18/ib-ehca-fix-maybe-uninitialized-warnings.patch
queue-3.18/net-ipv4-fix-multipath-rtm_getroute-behavior-when-iif-is-given.patch
queue-3.18/md-raid1-fix-a-dead-loop-when-read-from-a-writemostly-disk.patch
queue-3.18/net-avoid-signed-overflows-for-so_-snd-rcv-bufforce.patch
queue-3.18/mips-elf2ecoff-fix-warning-due-to-dead-code.patch
reply other threads:[~2017-05-04 23:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14939392781674@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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.