From: Jens Rottmann <Jens.Rottmann@ADLINKtech.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
<stable@vger.kernel.org>
Subject: 4.1.18 introduced spurious copy of renamed iwlwifi trans.c
Date: Mon, 25 Apr 2016 19:41:18 +0200 [thread overview]
Message-ID: <571E56BE.3030406@ADLINKtech.com> (raw)
Hi,
some time after 4.1
drivers/net/wireless/iwlwifi/pcie/trans.c
got moved to
drivers/net/wireless/intel/iwlwifi/pcie/trans.c
Later upstream commit 62d7476d958ce06d7a10b02bdb30006870286fe2
"iwlwifi: pcie: properly configure the debug buffer size for 8000"
fixed something in the new intel/iwlwifi/pcie/trans.c
The patch was backported and included in 4.1.18 as commit
d9d42b679e3653759b107ff99daf8da9c21aaec7. It does nicely apply to the
old file iwlwifi/pcie/trans.c, _however_ by mistake the patch also
introduces a useless copy of the complete file at it's modern home
intel/iwlwifi/pcie/trans.c
The 'fix' would be to delete the surplus file again. I don't know if you
want this, the 2nd copy of trans.c is never compiled, so strictly
speaking it does no harm - except that it confused me enough to write
this mail. :-)
Regards,
Jens
reply other threads:[~2016-04-25 17:41 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=571E56BE.3030406@ADLINKtech.com \
--to=jens.rottmann@adlinktech.com \
--cc=emmanuel.grumbach@intel.com \
--cc=sasha.levin@oracle.com \
--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 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).