From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S3C24XX: drop "select MACH_N35"
Date: Thu, 7 Mar 2013 09:32:02 +0000 [thread overview]
Message-ID: <20130307093202.GC17833@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <015001ce1ad1$185e66d0$491b3470$%kim@samsung.com>
On Thu, Mar 07, 2013 at 10:14:19AM +0900, Kukjin Kim wrote:
> Russell King - ARM Linux wrote:
> > And deleting entries from it is pointless if they've ever been in the
> > kernel.
>
> OK, I see and agree.
The issue is that the database system "locks" an entry into the file as
soon as support is merged into mainline for the platform. The reason
for this is that as soon as the support gets merged into a kernel verison,
that symbol is then referenced.
If anyone goes to the website to download a new copy of the file, it then
must continue to contain that symbol because they may be using the file
with any kernel version - maybe a version of the kernel with your platform
support in - and maybe they're using something that references the
generated ID/macros from your entry.
Updates to the file in the mainline kernel are merely re-downloads of the
file from the website and committed.
So, deleting entries once used in mainline is extremely problematical. If
someone commits such a patch, my next update from the website/database to
the file will put it back. Hence the problem.
prev parent reply other threads:[~2013-03-07 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 22:33 [PATCH] ARM: S3C24XX: drop "select MACH_N35" Paul Bolle
2013-03-07 0:02 ` Kukjin Kim
2013-03-07 0:11 ` Paul Bolle
2013-03-07 0:50 ` Kukjin Kim
2013-03-07 0:52 ` Russell King - ARM Linux
2013-03-07 1:14 ` Kukjin Kim
2013-03-07 9:32 ` Russell King - ARM Linux [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=20130307093202.GC17833@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).